LogIn

Validation Support

 Home / Support / Validation Guide

DV, OV, EV process guide


Domain validation provides fast and easy validation. It can be verified by choosing between email verification, hash verification, and DNS verification. Domain validation certificate does not contain business information.

Email Verification

The method of validation using an email address allowed by the certification authority.

for example :
administrator@yourdomain.com
webmaster@yourdomain.com
hostmaster@yourdomain.com
postmaster@yourdomain.com ... etc


HTTP/HTTPS File Verification

HTTP based DCV requires that a HTTP server be running on port 80 or that an HTTPS server be running on port 443 of the Authorization Domain Name that exactly matches the FQDN for which the certificate is requested.
Digicert(Thawte, Geotrust, RapidSSL)
http(s)://(www.)FQDN/.well-known/pki-validation/authfile.txt
Sectigo
http(s)://(www.)FQDN/.well-known/pki-validation/{md5 hash value}.txt
Certum
http(s)://(www.)FQDN/.well-known/pki-validation/certum.txt
* This method cannot be used for validating certificates with Wildcard names.


DNS CNAME or TXT Verification

A CNAME record cannot co-exist with another record for the same name. It's not possible to have both a CNAME and TXT record for www.example.com . A CNAME can point to another CNAME, although this configuration is generally not recommended for performance reasons.

DNS CNAME based DCV requires the creation of a unique CNAME record, pointed back to Sectigo.
We look for the CNAME at every valid Authorization Domain, i.e. we start with the FQDN and then we will strip one or more labels from left to right in the FQDN and will look for the CNAME on each intermediate domain. .

TXT Example
HOSTName           Type            VALUE
                   TXT             xxxxxaaaaaxxxxxxxxxx_CA_Value
CNAME Example
HOSTName           Type            VALUE
_ca_host_id        CNAME            xxxxxaaaaaxxxxxxxxxx_CA_Value