Website Security

All three provide the same TLS encryption strength, the difference is how thoroughly your organization's identity is verified before issuance. DV (Domain Validation) confirms control of the domain and typically issues in minutes. OV (Organization Validation) verifies your legal business identity against independent sources; the validated organization name appears in certificate details. EV (Extended Validation) applies the strictest identity verification under CA/Browser Forum EV Guidelines, used for high-trust sites where visible verified identity matters. Choose DV for developer and internal sites, OV for commercial business sites, and EV for financial services, government, and any site where the visitor should see cryptographic proof of your organization's legal identity.

Wildcard covers one domain and unlimited subdomains beneath it (*.yourdomain.com), ideal when you have many subdomains under the same apex domain, especially dynamic or auto-provisioned ones. Multi-Domain (UCC/SAN) covers up to 500 completely different domains in one certificate, required for Microsoft Exchange hybrid and OCS environments, and efficient when you operate several distinct domains. You can also combine the two: a Multi-Domain certificate can include wildcard SANs for maximum coverage across a multi-domain portfolio with subdomains.

ACME (Automatic Certificate Management Environment, RFC 8555) is the industry-standard protocol for automated certificate issuance, renewal, and revocation. ACME clients handle the full lifecycle without portal interaction; your TLS certificates renew themselves. Automation has moved from convenience to necessity. Effective March 2026, maximum TLS lifetimes dropped to 200 days. The CA/Browser Forum has approved further reductions toward 47 days by 2029. Manual renewal at that cadence isn't operationally viable for fleets of any size. SSL.com supports the full ACME v2 specification with no artificial rate limits, compatible with cert-manager, Caddy, Traefik, Certbot, acme.sh, and every standard ACME client.

As of March 11, 2026, the maximum TLS certificate lifetime is 200 days under CA/Browser Forum Baseline Requirements. The CA/B Forum has approved further reductions staged toward 47-day maximum lifetimes by 2029. Organizations managing more than a handful of certificates should plan for automated renewal via ACME. Manual renewal at 47-day cadence across even a modest fleet is operationally unsustainable. SSL.com's ACME product is designed for exactly this transition.

Yes. SSL.com TLS/SSL certificates chain to publicly trusted roots included in every major browser, operating system, and cloud platform trust store. Compatible with Apache, Nginx, IIS, Tomcat, AWS Certificate Manager (as imported certificates), AWS Application Load Balancer, Google Cloud Load Balancer, Azure Application Gateway, and every major CDN platform including Cloudflare, Akamai, Fastly, and AWS CloudFront. For cloud-native deployments, SSL.com's ACME support means cert-manager on Kubernetes (EKS, GKE, AKS) can issue and renew certificates automatically against SSL.com as the CA endpoint.