Domain Control Validation (DCV) is how a Certificate Authority confirms you actually control the domain before it issues a certificate. Every SSL/TLS certificate requires it. There are three methods; SSLStore.in defaults to the strongest and shows you exactly what to do.
DNS validation (recommended)
You add a small DNS record to your domain - a CNAME (Sectigo/Comodo) or TXT (DigiCert) record we generate for you. It is cryptographic, works for wildcard certificates, and can be reused for automation. This is the industry's long-term standard and our default.
HTTP file validation
You upload a small text file we provide to http://yourdomain.in/.well-known/pki-validation/. Good if you can't edit DNS but can publish files. Two limits: it can't be used for wildcard certificates, and it validates only the exact domain, not its subdomains.
Email validation (legacy)
The CA emails a link to a constructed address on your domain - admin@, administrator@, hostmaster@, postmaster@ or webmaster@. This method is being phased out across the industry and is scheduled for full retirement by 2028, so we keep it only as a labelled fallback.
A note on DNSSEC
Since 15 March 2026, CAs validate DNSSEC signatures during DNS lookups. If your domain has misconfigured DNSSEC, DNS validation (and issuance) will fail until it's fixed. If you don't use DNSSEC at all, nothing changes.
Which method should you use?
Use DNS unless you can't edit your DNS zone, in which case use the HTTP file method. Leave the record or file in place until the certificate is issued - if you remove it too early, validation can fail. Ready to set up? See how to activate your certificate.
Not sure your record is live yet? Check it with the DNS, DCV & CAA Checker.