This article contains no advertisements or affiliate links. We checked TLS standards, certificate requirements, browser behavior and HTTPS migration against official sources. It does not recommend a contract with a particular CA or server provider.
Modern HTTPS connections use TLS. SSL is the name of an older protocol, but survives in phrases such as 'SSL certificate' and 'free SSL'. Do not stop after obtaining a certificate: check the host names, chain, TLS settings, HTTPS redirects, mixed content and deployment after renewal.
SSL is the older name; TLS 1.2 and 1.3 protect current connections
A certificate helps verify the destination; the TLS channel provides encryption. Public certificate maximum validity periods are shortening from 2026, making automatic renewal and external monitoring important.
| Protocols in current use | TLS 1.2 and TLS 1.3 |
|---|---|
| The certificate's role | Presents signed host names and public keys to help verify the destination |
| Maximum validity in 2026 | 200 days(for public TLS certificates issued from March 15, 2026 through March 14, 2027) |
| Completion criteria | Check certificates, TLS settings, HTTP redirects, mixed content, critical functions and deployment after automatic renewal |
| Previous overall review | July 29, 2026 |
SSL and TLS in one sentence
SSL/TLS is a family of cryptographic protocols for authenticating peers and protecting data in transit between clients and servers from eavesdropping and tampering.
HTTPS carries HTTP over a secure TLS channel. At connection startup the browser and server negotiate supported TLS versions and algorithms, and the server presents a certificate chain. Once the browser verifies the host name, validity period and signatures, session keys protect the rest of the connection.
| Term | Meaning | Current use |
|---|---|---|
| SSL | Secure Sockets Layer, a communications security protocol preceding TLS. | Do not use SSL 2.0 or 3.0. The name remains common in phrases such as 'SSL certificate'. |
| TLS | Transport Layer Security, the successor to SSL and the basis of modern encrypted connections. | Existing websites use TLS 1.2 and 1.3. Newly designed protocols are moving toward requiring TLS 1.3. |
| HTTPS | HTTP sent over a TLS-protected channel. | Use HTTPS across the site, not just for login and payments. |
| SSL/TLS certificate | A signed digital certificate presenting a public key, covered host names, issuer and validity period. | Used to verify the destination. A certificate alone does not guarantee web application security. |
Even when a product says 'SSL', check the actual TLS version
A control panel may call it 'SSL settings', but real connections use TLS. Test the connection for allowed TLS 1.0 or 1.1 and obsolete cryptographic algorithms rather than relying on the label.
How certificates, HTTPS and certificate authorities relate
Separate four easily confused roles when troubleshooting: TLS is the communication protocol, HTTPS is HTTP over TLS, a certificate supplies identity-verification information, and a CA signs certificates.
Browser
Starts a TLS connection using the host name in the URL.
TLS endpoint
A CDN, load balancer or web server presents the certificate.
Certificate chain
Connects the server certificate through intermediate CAs to a trust anchor.
HTTPS communication
After verification, encrypted HTTP requests and responses are exchanged.
Key certificate checks
- subjectAltName (SAN) includes the host name being accessed.
- Not Before / Not After bounds the certificate's validity period.
- The server certificate can be validated through intermediates to a trusted root CA.
- The public key in the certificate matches the private key held at the TLS endpoint.
- Every TLS endpoint, including CDNs, load balancers and origin servers, serves the intended certificate.
A valid certificate does not guarantee the whole site is safe
A certificate helps establish that an entity receiving connections for a domain passed the required checks and presents the associated public key. A phishing site can also obtain a certificate for an attacker-controlled domain. Check the URL, operator, content and application security separately.
How does a TLS handshake begin?
A TLS handshake prepares the browser and server for encrypted communication. Details differ by implementation and resumed connection, but an initial connection can be understood as follows.
The client sends supported parameters
It sends a ClientHello containing supported TLS versions and algorithms, a random value and the SNI host name.
The server responds with its choice and certificate
It selects mutually supported parameters and presents a certificate chain and key-sharing information.
The browser validates the certificate
It checks the host name, validity period, signatures, chain and intended use. Failed validation causes a warning or connection failure.
Both sides derive session keys
They derive symmetric session keys from the key exchange; the private key itself is not sent over the network.
Start encrypted HTTPS communication
After the handshake, HTTP headers and bodies are exchanged as protected TLS records.
Observations differ with session resumption, HTTP/2, HTTP/3 and CDN configurations. When troubleshooting, distinguish the first TLS endpoint users reach from its connection to the origin.
What TLS can and cannot protect
TLS is a foundation of web security, not a universal safety certificate. Separate connection protection from application, device and operational measures.
Protections TLS directly provides
- Confidentiality: Makes data in transit difficult for third parties to read
- Integrity: Prevents undetected alteration of data in transit
- Server authentication: Verifies the destination using a certificate and host-name matching
Problems TLS alone cannot prevent
- Web application vulnerabilities such as SQL injection, XSS and authorization failures
- Stolen passwords, phishing and device malware
- Server compromise, exposed backups, leaked private keys and misconfiguration
- Encryption at rest, backups, least privilege and recovery procedures
Referencing HTTP images, JavaScript, CSS, iframes or form destinations from an HTTPS page creates mixed content. Browsers may automatically upgrade some resources, but block scripts and others, breaking layout or functionality. Fix the source URLs to use HTTPS.
Choosing an SSL/TLS certificate
Choose by the level of identity validation and the number of covered host names. Price or validation category alone does not determine encryption strength.
Validation levels: DV, OV and EV
| Type | What is mainly verified | Suitable uses | Considerations |
|---|---|---|---|
| DV | Control of the domain or IP address | General websites, blogs, APIs and a wide range of personal and business services | Does not verify the organization's legal existence. Ease of automatic issuance and renewal is a practical benefit. |
| OV | Applicant organization information as well as domain control | Organizations that need their information included in the certificate | Plan the checks and procedures for issuance and renewal in advance. |
| EV | A more rigorous process checks the organization's existence and the applicant's authority. | When contracts, regulations or internal policy require enhanced identity validation | Do not choose based on the green address bar used by older browser versions; major browsers no longer generally display it. |
Covered names: single, wildcard and multi-domain
Single domain
Covers one FQDN. Suitable when there are few targets or responsibilities should be separated.
Wildcard
*.example.comcovers subdomains at one level. It does not normally include the apex or subdomains two levels below automatically.
Multi-domain (SAN)
Includes several distinct FQDNs on one certificate. Consider management boundaries because renewal affects a wider scope.
Selection criteria
Decide based on required host names, renewal automation, key storage, revocation and reissuance, responsibilities and support.
Paid certificates do not necessarily provide stronger encryption than free ones
Actual connection strength also depends on key type, TLS version, cipher suites, libraries and server settings. Paid certificates may offer value in organization validation, warranties, support or management tools. Choose for your use and operations, then measure actual connections after deployment.
TLS and certificate operation changes to know in 2026
The TLS 1.3 standards document and certificate renewal intervals changed significantly in 2026. Procedures based on older guidance to renew once a year cannot be used unchanged.
RFC 9846 is the current TLS 1.3 specification
RFC 9846, published in July 2026, is the current TLS 1.3 specification. It replaces RFC 8446 and also specifies new requirements for TLS 1.2 implementations. RFC 9851 freezes TLS 1.2 changes except for urgent security fixes and exceptions such as new TLS Exporter labels and ALPN identifiers. RFC 9852 requires TLS 1.3 as the default for new protocols using TLS while allowing TLS 1.2 as a non-default option. We checked these three RFCs on November 3, 2026.
Existing websites may retain TLS 1.2 for compatibility, but should enable TLS 1.3 and disallow TLS 1.0 and 1.1. When using TLS 1.2, avoid enabling obsolete key exchanges or ciphers indiscriminately.
Maximum public TLS certificate validity is being reduced in stages
Plan for automated renewal, such as ACME, and external monitoring now
Even when a renewal job succeeds, a web-server reload can fail, a CDN deployment can be missed or another region can serve an old certificate. Monitor externally whether every TLS endpoint users reach presents the new certificate, not merely whether it was obtained.
Seven steps for deploying SSL/TLS and site-wide HTTPS
The same checking sequence applies to automated shared hosting and your own load balancer. A control panel saying 'enabled' is not enough; test the user's connection path.
Inventory host names and TLS endpoints
List the apex, www, APIs, administration, CDN, load balancer and other regions; map DNS destinations and certificate owners.
Choose the certificate and renewal method
Choose DV, OV or EV and single, wildcard or SAN coverage. Plan for automated renewal given the shorter validity periods from 2026.
Deploy the certificate, intermediates and private key correctly
Keep private keys out of public directories and Git, restrict access to the minimum necessary and check for missing intermediates.
Test critical functions over HTTPS first
Test not just the home page but login, forms, payments, APIs, WebSockets, images, downloads and external integrations.
Permanently redirect HTTP to HTTPS
Use 301 or 308 redirects to the corresponding URL, avoiding loops and unnecessary chains. Verify that paths and query strings are preserved.
Update internal URLs and security settings for HTTPS
Update canonical URLs, sitemaps, internal links, OG URLs, APIs and form destinations; check the Secure cookie attribute. Introduce HSTS gradually after HTTPS is stable on every affected host.
Continuously monitor renewal, expiry and alerts
Monitor renewal results, actually served certificates, expiry, name mismatches, chains and TLS versions externally, and test alert delivery regularly.
How to check SSL/TLS settings
One method can miss problems. Check using browsers, commands, external tests and actual functions.
Check the certificate and TLS version in a browser
In Chrome, do not treat HTTPS as a 'lock icon' proving the entire site's trustworthiness. Open connection information from the site-information or controls icon at the left of the address bar, or use the Security panel in developer tools to check the certificate, protocol and ciphers. Check certificate details and warnings in Safari and Edge too; do not declare success from one device.
Check the public path with OpenSSL and curl
# Check the presented certificate, issuer, validity and SAN
openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null \
| openssl x509 -noout -subject -issuer -dates -ext subjectAltName
# Check the HTTP-to-HTTPS redirect
curl -I http://example.com/
# Before changing DNS, connect to the new IP with SNI and the host name preserved
curl --resolve example.com:443:203.0.113.10 https://example.com/ -I
A successful command alone is not enough. Read the host name, validity period, issuer, SAN, verification errors, redirect destination and status code. Available options differ by OpenSSL version.
Assess the public configuration with an external test
Use a completion checklist
Why warnings can appear despite a valid certificate
If a warning persists after renewal, start with the TLS endpoint the user actually reaches and the browser's error message.
| Symptom or cause | Where to check | Possible response |
|---|---|---|
| Host-name mismatch | URL, SAN, SNI, presence of www and API subdomains | Include the accessed FQDN in the certificate and assign the correct certificate to the TLS endpoint. |
| Expired or not yet valid | Not Before / Not After, device clock and renewal job | Repeat renewal and deployment, add external monitoring and check the device clock. |
| Incomplete chain | Intermediate certificates served and differences between clients | Deploy the full chain with the appropriate intermediates; avoid including unnecessary root certificates. |
| Old certificate remains | CDN, load balancers, multiple regions and IPv4/IPv6 | Check every path separately and reload, deploy or refresh caches as needed. |
| Mixed content | DevTools Console/Network, HTML, CSS, JS, APIs and forms | Update HTTP references to HTTPS and verify that external resources support HTTPS. |
| Redirect loop | Proxy X-Forwarded-Proto, application scheme detection and CDN settings | Clarify responsibilities of the TLS endpoint and application, and centralize HTTPS detection. |
| Only some older devices fail | Supported TLS versions, trust stores, certificate chains and ciphers | Decide the required compatibility range and assess security trade-offs. |
How does HTTPS affect SEO?
Google recommends HTTPS to improve user and site security. Installing a certificate does not guarantee higher rankings; helpful content and relevance to search intent also matter. HTTPS is a foundation for secure communication and page experience and helps avoid HTTP warnings and restrictions. We checked Google's official guides on November 3, 2026.
When URLs change from HTTP to HTTPS, treat it as a site move. Implementation mistakes can create duplicate URLs, split crawling, missing images or broken forms, so align the following items.
- Redirect each HTTP URL server-side to its corresponding HTTPS URL with 301 or 308
- Update canonical, hreflang, OG and structured-data URLs to HTTPS
- Use HTTPS in XML sitemaps and internal links, and check Search Console
- Check that robots.txt, CDN and WAF do not block Googlebot from HTTPS
- Do not stop old HTTP redirects prematurely; monitor traffic and crawling
- Compare Core Web Vitals, mobile display, mixed content and critical conversions before and after migration
A certificate's price or brand does not directly raise search rankings
Users and Googlebot need reliable HTTPS access to the correct page content. Choose free or paid certificates based on validation scope, renewal, support and management requirements.
Frequently asked questions about SSL/TLS and certificates
Are SSL and TLS the same?
Strictly speaking, no. SSL is the older protocol preceding TLS; modern secure web connections use TLS. The term remains shorthand in phrases such as 'SSL certificate', 'free SSL' and 'always-on SSL'.
Does a paid certificate provide stronger encryption than a free one?
Price does not determine it. DV, OV and EV mainly differ in the information checked at issuance. Connection strength also depends on keys, TLS versions, ciphers and server settings. Choose by required organization validation, support, management and renewal.
Does a lock icon mean a site is safe?
It does not guarantee site-wide safety. Chrome replaced the traditional lock with a neutral site-information icon so HTTPS would not be interpreted as a special mark of trustworthiness. HTTPS protects the connection, but fraudulent sites, application vulnerabilities, deceptive content and device malware are separate issues.
Does automatic renewal prevent certificate expiration?
Automatic renewal is a near-essential measure, but not enough alone. Failed validation, permission changes, missed deployment or failed server reloads can leave an old certificate in use after a successful job. Monitor expiry and the actual served certificate externally.
Does a wildcard certificate protect every subdomain?
Usually, *.example.com covers a single level such as www.example.com, but does not automatically include the apex example.com or a two-level subdomain such as api.dev.example.com. Check the SAN for every required name.
Is an SSL Labs A grade enough to complete the setup?
It is valuable evidence about public TLS settings, but not completion on its own. HTTP redirects, mixed content, login, forms, payments, APIs, cookies, deployment after renewal and internal hosts need separate operational checks.
Can a move to HTTPS reduce search rankings?
HTTPS itself is not a disadvantage when the move is done correctly. Missing redirects, incorrect canonical URLs, mixed internal links, outdated sitemaps or blocked crawling can cause temporary changes or split indexing. A URL mapping and monitoring before and after migration matter.
SSL/TLS is complete only after verification and renewal operations
Modern HTTPS uses TLS. SSL remains common shorthand for certificates and services, but check TLS 1.2 and 1.3 support, certificate chains, host names, validity, HTTPS redirects and mixed content.
Shorter certificate validity from 2026 makes automated renewal and external monitoring important.Check not just renewal job success but that every TLS endpoint—including CDNs, load balancers and web servers—actually serves the new certificate.
- SSL is the old protocol name; TLS protects modern connections
- Certificates help verify destinations; they do not certify the safety of the whole site
- Check redirects, internal URLs, mixed content and critical functions together during HTTPS migration
- After launch, monitor expiry, name mismatches, chains, TLS settings and deployment after renewal
Standards and official guidance checked
As of July 29, 2026, we checked definitions, recommended versions, certificate validity, host-name matching, mixed content, HTTPS migration and browser display against these sources.
- RFC 9846: The Transport Layer Security (TLS) Protocol Version 1.3
- RFC 9851: TLS 1.2 is in Feature Freeze
- RFC 9852: New Protocols Using TLS Must Require TLS 1.3
- RFC 8996: Deprecating TLS 1.0 and TLS 1.1
- RFC 9525: Service Identity in TLS
- RFC 5280: Internet X.509 Public Key Infrastructure Certificate and CRL Profile
- RFC 10015: Deprecating Obsolete Key Exchange Methods in TLS 1.2 and DTLS 1.2
- CA/Browser Forum: Latest Baseline Requirements
- OWASP: Transport Layer Security Cheat Sheet
- Let's Encrypt: Challenge Types
- MDN Web Docs: Mixed content
- Chromium Blog: An Update on the Lock Icon
- Google Search Central: Site Moves and Migrations
- Google Search Central: Understanding page experience
- Qualys SSL Labs: SSL Server Test