Skip to main content

Domain control validation (DCV) methods

Supported DCV methods for validating the domains on DV TLS/SSL certificate orders

Before DigiCert can issue a DV TLS certificate, you must prove control over the domains and any SANs (subject alternative names) on the certificate. We refer to this process as the DCV process.

A DV TLS certificate's domain validation is valid long enough to issue the certificate. DV domain validation isn’t reusable for reissues or renewals. Each time you order a DV certificate, you must demonstrate control over the domains on the order before DigiCert can issue your DV TLS certificate.

For DV certificates in CertCentral, DigiCert currently supports the following DCV methods:

  • Email

    • Email to DNS TXT contact

    • Constructed email

    Warning

    End of life for the WHOIS-based Email

    On May 8, 2025, DigiCert ended support for the WHOIS-based domain control validation method (DCV) email method. DigiCert systems have stopped querying WHOIS entirely to find email addresses for domain validations. To learn more about this change, see our knowledge base article, End of life for WHOIS-based DCV methods.

    What should I do?

    Update your domain validation process to use one of the other supported DCV methods. To continue using the Email DCV method, use the DNS TXT record email contacts or the Constructed email method.

  • DNS TXT

  • DNS CNAME

  • HTTP Practical Demonstration

Email DCV method

With this validation method, DigiCert sends two sets of DCV emails: DNS TXT-based and constructed.

To demonstrate control over the domain, an email recipient follows the instructions in a confirmation email sent for the domain. The confirmation process consists of going to the link provided and following the instructions on the confirmation page.

Note: DigiCert sends this email from no-reply@digitalcertvalidation.com. If using allowlist, make sure to include digitalcertvalidation.com.

Email to DNS TXT contact

With this method, DigiCert sends an authorization email to the address in the DNS TXT record on the _validation-contactemail subdomain of the domain being validating. While validating a domain, make sure to select the Verification email DCV method.

To configure your CertCentral Email DCV method to send the confirmation email to DNS TXT contacts, do the following:

  1. Place the DNS TXT record on the _validation-contactemail subdomain of the domain you want to validate. The RDATA value of this text record must be a valid email address.

    Name

    TTL

    Message

    _validation-contactemail

    Default

    validatedomain@digicerttest.com

    DigiCert recommends adding a distribution list rather than a personal email address. A distribution list allows you to create a "non-expiring" email address to which you can add or remove people if necessary.

  2. Update your CertCentral account settings to send the verification DCV emails to Org/Tech/Admin contacts from DNS TXT.

    1. In CertCentral, in the left menu, go to Settings > Preferences.

    2. On the Preferences page, select Advanced Settings.

    3. In the Domain Control Validation (DCV) section under Send verification DCV emails to, select Org/Tech/Admin contacts from DNS TXT.

    4. Go to the bottom of the page and select Save Settings.

  3. See our instructions for Using Email verification to validate a domain on a DV TLS certificate

Constructed email

For the Constructed Email method, DigiCert sends the authorization email to five constructed email addresses for the domain: admin, administrator, webmaster, hostmaster, and postmaster @[domain_name].

If we can't find an MX record for [domain_name], use another supported DCV methods to demonstrate control over the domain. See MX records (mail exchanger records).

Background

While registering a domain, you must provide contact information, such as administrative and technical contacts. Instead of using a personal email address, you can use one of the constructed email addresses for your domain, such as webmaster@yourdomain. Using a constructed email address allows you to create a "non-expiring" email address that you can add or remove people from if necessary.

MX (Mail Exchanger) records

To send an authentication email to the domain controller, we must verify an MX record exists in the DNS records of the recipient's domain. The presence of valid MX records enables us to send the authentication email. An MX record is a resource record in the Domain Name System [DNS].

For example, you want us to send the DCV email to a constructed email addresses for example.com, such as admin@example.com. To email admin@example.com, we must find an MX record for the address identifying the server set up to receive emails for admin@example.com.

DNS TXT DCV method

With this validation method, add a DigiCert-generated random value to the domain’s DNS as a TXT record. Once DigiCert checks for a DNS TXT record for the domain, we can find a record that includes the DigiCert-generated random value.

DNS CNAME DCV method

If your domain has a CNAME record pointing to another domain (for example, yourdomain.com points to yourdomain.net), use this method to validate your domain.

With this validation method, you add the static prefix _dnsauth to DNS as a CNAME record in the hostname field. Then, add [random_value].dcv.digicert.com as the CNAME target. Once DigiCert checks for a DNS CNAME record for your domain, we can find a record that includes the DigiCert-generated random value.

HTTP Practical Demonstration DCV method

Use the HTTP Practical Demonstration DCV methods to demonstrate control over fully qualified domain names (FQDNs) exactly as named in the certificate request. To learn more, go to Domain Validation Policy Changes.

Validating IPv4 and IPv6 address

Per industry regulations, you must use the HTTP Practical Demonstration DCV method to demonstrate control over IPv4 and IPv6 addresses.

Use one of the other supported DCV methods to:

  • Validate wildcard domains, such as *.example.com.

  • Include subdomains in the validation while validating a higher-level domain. For example, if you want to cover www.example.com, mail.example.com, and one.example.com while validating the higher-level domain example.com.

  • Validate entire domains and subdomains.

Using HTTP Practical Demonstration

With this method, host a file containing a DigiCert-generated random value at a predetermined website location: [domain]/.well-known/pki-validation/fileauth.txt. Once the file is created and placed on your site, DigiCert goes to the specified URL to confirm the presence of our random value.