Certamira
Independent reseller and guide. Not a certificate authority and not affiliated with any certificate authority.

CSR and DNS domain validation for a wildcard certificate

A CSR is a request made on your own server together with a private key. The private key stays with you and is not in the CSR. The seller checks control of the domain, for a wildcard by a DNS record. Validation data is reused for a limited time. Do not send the private key or the CSR to this site; pass the request only to the seller that issues the certificate.

What is a CSR?

A CSR is the certificate request file that carries the public key and the name you ask to place on the certificate. It does not carry the private key. The flag -newkey generates a new private key and a certificate request so the public key goes into the request and the private key is written to the file named by -keyout and is never sent to the seller.

Create a CSR for a wildcard

Create the key and the request with the command from the OpenSSL documentation.

openssl req -newkey rsa:2048 -keyout key.pem -out req.pem

The private key is written to key.pem and the request is written to req.pem. The same documentation shows how to set a name with -addext "subjectAltName = DNS:foo.co.uk". For a wildcard the name is written as DNS:*.example.com.

DNS validation step by step

Order of work: create the key and the request, send the request to the seller, publish the DNS record the seller names, then wait for the seller to read it.

The seller gives a value and you publish a DNS record and the CA reads it. The ACME DNS-01 method (RFC 8555 section 8.4) uses a TXT record at the name _acme-challenge followed by the domain. Let's Encrypt says a CNAME can point _acme-challenge to another zone and Sectigo describes a CNAME to a CA target or a TXT record at _pki-validation.your-domain.com with a CA value. For wildcard certificates the Baseline Requirements allow DNS change as a validation method (3.2.2.4.7) and do not mark HTTP-based file methods for wildcards.

How long is validation reused?

Reuse of domain validation is set out in section 4.2.1. The reuse period is 200 days from 15 March 2026. The reuse period is 100 days from 15 March 2027 and 10 days from 15 March 2029.

Checked on 4 November 2026. Source: OpenSSL documentation; RFC 8555; CA/Browser Forum Baseline Requirements v2.2.7.