Validate the request
Confirm domain control and complete the identity checks required by the selected certificate. The issuing authority determines acceptance.
SSL CERTIFICATES / TLS FOR YOUR WEBSITE
Choose HTTPS coverage for your website, application or other service. Compare validation categories, then confirm the hostnames and installation requirements before ordering.
Illustrative certificate. No certificate is issued in this preview.
CERTIFICATE SELECTOR
DV focuses on domain authorisation or control. It is a practical option when your requirement is a publicly trusted TLS certificate without organisation identity details.
OV combines domain validation with checks on the organisation’s identity. It suits organisations whose requirements call for verified company information in the certificate.
EV uses a more extensive legal-entity verification process. Choose it where your procurement, identity or policy requirements call for that validation scope.
Prepare: A working DNS or website validation method.
Request certificate guidanceVALIDATION AND COVERAGE
| Requirement | DV | OV | EV |
|---|---|---|---|
| Domain control check | Required | Required | Required |
| Organisation identity | Not part of DV identity validation | Organisation checks | Extended legal-entity checks |
| Primary consideration | Domain-based HTTPS requirement | Verified organisation details | Formal extended-validation requirement |
| Hostname coverage | Choose the exact names required. Single-name, multi-name and wildcard options depend on the issuing product and validation rules. | ||
| Connection encryption | All three are TLS certificate types. A higher validation category does not by itself create stronger connection encryption. | ||
| Price and issuance time | Confirmed by the selected certificate authority, product and validation process before your order. | ||
FROM REQUEST TO RENEWAL
Confirm domain control and complete the identity checks required by the selected certificate. The issuing authority determines acceptance.
Deploy the certificate and chain on the intended endpoint. Check the hostname, redirects, expiry and the relevant application configuration.
Schedule renewal, revalidation and deployment together. Verify the certificate running on the live endpoint; a renewal order alone is not confirmation that deployment is complete.
PREPARE YOUR CERTIFICATE REQUEST
Tell us where TLS terminates: your web server, reverse proxy, load balancer or another service. Identify the names and the people who control DNS and deployment.
Validation concepts follow the CA/Browser Forum’s requirements. Product availability and current rules must be confirmed with the issuer.
CERTIFICATE QUESTIONS
SSL is still a common product label, while modern HTTPS connections use TLS. Your certificate and server configuration should be planned around the current platform and security requirements.
Validation categories describe identity checks. They do not, by themselves, determine stronger connection encryption. TLS configuration, supported protocols and the cryptographic choices also matter.
No. A TLS certificate supports an authenticated encrypted connection to the covered endpoint. It does not replace application updates, access controls, backups, malware protection or secure development.
Timing depends on the issuer, product, validation method and the accuracy of the supplied information. Do not assume instant issuance or a fixed validity period; confirm the current process when ordering.
Wildcard coverage has naming limits and depends on the certificate product and validation type. List the exact hostnames you need, including any deeper subdomain levels, so the required coverage can be checked.
CONNECTED SERVICES
Share the exact hostnames, deployment platform and required validation category so coverage and installation can be reviewed together.