Domain Validation
The CA checks control of the requested names. DV does not verify the organization’s legal identity.
Compare DV certificates SSL guides & resources
SSL certificate validation: what you need to prepare
Payment, domain validation and certificate issuance are separate steps. Prepare the right access and records before you order.
Which checks apply?
Validation describes identity checks, not a ranking of encryption strength.
Organization Validation
Domain control plus checks on the organization using the CA’s required records and verification process.
Compare OV certificates 
Extended Validation
Additional organization verification under EV requirements. Confirm product availability and document requirements before ordering.
Explore EV requirements Choose a supported domain-control method
The available method depends on the certificate authority, product and requested names. Common options include a DNS record, a validation file on the website or an eligible administrative email address. Use the exact record name, value, file or recipient supplied for the order. A generic example copied from a guide will not validate your domain.
Wildcard validation has method restrictions. Confirm the permitted DNS procedure before ordering, especially when another department or provider controls DNS. For Let’s Encrypt wildcard certificates, DNS-01 is required. Do not assume a website-file challenge is available for every product.
Prepare access and organization details
- List the exact domains and subdomains to include.
- Identify who can update authoritative DNS, publish a validation file or access the eligible mailbox.
- For OV/EV, prepare accurate organization identity and contact details consistent with the CA’s requested records.
- Generate the CSR on the intended platform where required, and retain the matching private key securely.
- Coordinate centrally managed government or corporate infrastructure with its responsible technical team.
Resolve a pending validation
Check the method and current instructions in the order. DNS changes must be publicly visible at the authoritative provider. A file must be reachable at the required location; proxy rules, authentication and redirects can interfere. Organization discrepancies or missing verification responses may also delay review.
Share the domain, order reference, chosen method and a redacted error message with support. Do not submit passwords or private keys in an enquiry. Payment confirmation does not bypass CA checks, and no universal issuance time can be promised.
After issuance
Install the certificate and required chain on the endpoint visitors actually reach, then verify the served names, expiry and HTTPS behavior. Issuance alone does not deploy the certificate. Use installation guidance and plan renewal and replacement before expiry.
Common questions
Does paying for SSL complete validation?
No. Payment review, CA validation, issuance and installation are distinct stages. The CA must complete the applicable checks before issuance.
Can SSLS validate a domain without administrator access?
The responsible domain or hosting administrator must perform the required control check, or provide the authorized access through an agreed secure process. Do not share private keys or passwords in the initial enquiry.
How long does SSL validation take?
It depends on the chosen method, DNS or hosting access, accurate organization information and the CA’s review. Resolve the specific pending action rather than relying on a guaranteed number of minutes.
Will renewal require validation again?
Follow the instructions for the replacement or renewal order. Validation reuse rules and CA requirements can change; do not assume a previous approval guarantees automatic issuance.