Here's a detailed KB article explaining how to verify domain ownership (Domain Validation) during the SSL certificate issuance process. This is applicable for DV, OV, and EV certificates.
Before issuing an SSL certificate, a Certificate Authority (CA) must confirm that the requester owns or controls the domain. This process is called Domain Validation (DV) and is mandatory for all types of SSL certificates (DV, OV, and EV).
This article explains the 3 standard domain validation methods used by CAs:
Email-Based Validation
DNS-Based Validation
HTTP File Upload Validation
Any individual or organization purchasing an SSL/TLS certificate
Applies to Domain Validated (DV), Organization Validated (OV), and Extended Validation (EV) certificates
OV/EV certificates also require business verification, but domain control is still mandatory
Step-by-Step:
When ordering the SSL, select Email Validation as the method.
CA sends a confirmation email to domain-based addresses, such as:
Open the email and click the verification link.
Once confirmed, the certificate is issued.
β Pros:
Easy for most users with access to domain email
β Cons:
Requires the domain to have one of the above email addresses set up
This method involves creating a DNS TXT record that the CA will check to confirm ownership.
Step-by-Step:
During SSL order, select DNS Validation.
CA will provide a unique TXT record like:
Log into your DNS provider (Cloudflare, GoDaddy, Route 53, etc.).
Create the TXT record as instructed.
Save and wait for DNS propagation (can take 5β30 minutes).
CA will verify the record automatically.
β Pros:
No need for email or website access
β Cons:
Requires DNS management access
Propagation delay may affect issuance time
CA provides a file that must be uploaded to a specific path on your web server.
Step-by-Step:
Choose HTTP File Validation during SSL setup.
CA provides a file like:
Filename:
.well-known/pki-validation/abc12345.txt
Contents:
A long token string for verification
Upload this file to:
Ensure itβs publicly accessible via browser.
CA will access the file to confirm ownership.
β Pros:
No email or DNS changes needed
β Cons:
Requires FTP/SSH or access to web root
Cannot be used for domains that donβt have live hosting
Yes, most Certificate Authorities allow you to switch methods before the certificate is issued.
If one method fails:
Retry with another method via your CA's control panel or support
DNS is often the fallback when others fail
Issue | Solution |
---|---|
Email not received | Check spam/junk, ensure correct domain alias is set up |
DNS record not found | Verify record format, TTL, and propagation |
HTTP validation fails | Confirm public access, correct file path, no redirects or SSL enforcement |
Using Cloudflare | Temporarily disable proxy (orange cloud ) for _acme-challenge DNS entries |
Only use validation tokens provided by your CA.
Tokens expire if not used in time (usually 24β72 hours).
Donβt reuse old tokens or reuse the same CSR for another domain.