Guides SSL / TLS

What is an SSL/TLS certificate?

How does a browser check a secure connection to example.com? See what your host configures and how to monitor certificates.

A visitor opens your website at https://example.com. The browser sets up an encrypted connection to prevent eavesdropping and changes in transit. It also checks that the server belongs to that domain name. The digital proof used for that check is called a TLS certificate.

Check SSL / TLS on your own domain

What happens at example.com?

The example.com server sends its certificate to the browser. The browser checks, among other things:

  • Does this certificate cover example.com?
  • Is it valid now?
  • Does it come from an issuer the browser trusts?

A trusted issuer is called a Certificate Authority, or CA. Intermediate certificates may link the server certificate to that trusted issuer. Together they form the certificate chain. When the check succeeds, the browser can use the secure connection to that domain name.

An ordinary domain certificate does not prove a business's identity or good intentions. As a visitor, also check that this is the real domain you intended to open. Extra company checks for some certificates do not automatically make the contents safe.

What your host or administrator needs to configure

With managed hosting, the host normally provides the certificate. Ask who manages renewal and who receives failure alerts. On your own server, an administrator must configure a client or platform to request, renew and install certificates on the correct service. ACME is the usual protocol such software uses to automate requests. The CA does not take over your server administration.

Check together that:

  • The certificate covers every visited name, such as both example.com and www.example.com where both are used. These names appear in Subject Alternative Name (SAN).
  • Every public endpoint presents the right certificate: a CDN, load balancer or second server may have its own installation.
  • The server supplies the required intermediate certificates so browsers can build a trusted chain.
  • A successful renewal is actually deployed and the service reloads its certificate where necessary.
  • An external check of name, chain and expiry, plus failure alerts to a responsible person, monitors the process.

Issuing a new certificate is not enough. The server also needs to present it before the old one expires.

Validity and renewal

Maximum lifetimes for newly issued, publicly trusted TLS server certificates are getting shorter: from 15 March 2026 the limit is 200 days, from 15 March 2027 it is 100 days, and from 15 March 2029 it is 47 days. A CA can choose a shorter lifetime. Let's Encrypt's default profile is 90 days, but shorter profiles are also available.

Automate renewal well before expiry, including installation and verification. Do not rely only on a scheduled job configured long ago: check whether renewals succeed and which certificate visitors actually receive. Pay particular attention to manually managed certificates and have an administrator investigate failed requests.

Investigating a warning

Browsers display connection status differently. A neutral site icon instead of a padlock may be normal. Read the connection information and specific warning rather than relying on the presence of a padlock. Open the icon next to the address and look for security or certificate details. The exact steps vary by browser.

A different browser icon does not necessarily mean a fault. For an actual connection warning, note the error and exact hostname visited. Then have these checked:

  • Expiry: has the certificate expired, or is an old installation still being served?
  • Domain name: does the certificate cover only example.com while you are opening www.example.com?
  • Trust chain: are intermediate certificates missing, or is the issuer untrusted?
  • Server settings: does the browser reject an old TLS version or weak configuration?
  • Mixed content: does an HTTPS page still load parts over HTTP? Browsers may block them or show a warning.

With managed hosting, send the hostname and error to your host. An administrator tests the affected TLS endpoint and then checks what it serves externally. Do not advise visitors to click through certificate warnings.

What DNS Radar checks

The domain button opens a DNS scan. It examines, among other things, addresses, CAA, and published HTTPS/SVCB and TLSA information. Such publication does not prove a successful HTTPS connection.

DNS Radar does not retrieve the live website certificate in that scan or test your website's expiry, chain or TLS version. View the certificate details at the actual website in your browser, and have your administrator run a separate TLS endpoint test when needed. A positive DNS result is not a certificate inspection.

CAA and CT logs

CAA is a DNS record declaring which certificate authorities may issue for your domain. It does not renew or repair an installed certificate. The CAA guide explains who can help choose the authorized issuers.

Certificate Transparency (CT) makes the issuance of publicly trusted TLS certificates auditable through public logs. Browser policies set requirements for that logging. It is not a complete register of all private, email or other certificates.

A log may contain a certificate or a precertificate: an announcement before issuance. It does not record every individual application or prove that the certificate is currently used on a server. If you see an unfamiliar entry for your domain, first check the names, issuer and your own hosting or CDN. Then have your administrator and the issuer investigate any suspected unauthorized issuance.

Primary sources

Frequently asked questions

Is SSL the same as TLS?

SSL is the old, unsafe predecessor of TLS. The term ‘SSL certificate’ is still widely used, but modern websites use TLS. A server should offer current secure settings. TLS 1.2 and 1.3 are the usual versions, while older versions are deprecated.

Do I need a paid certificate?

For most sites, a free certificate from a trusted issuer is sufficient. Paying does not automatically provide stronger encryption. It may come with different services, warranties or company validation. Choose what your environment needs.

My padlock is gone. What now?

A neutral site icon may be normal. Open the connection information and check whether there is an actual warning. For an error, note the hostname and message and have the expiry, name, chain and server settings checked. Without a warning, a different icon alone does not prove a certificate problem.

My domain appears in a CT log. Is that abuse?

Not necessarily. Your host or CDN may legitimately request certificates. An entry may also be a precertificate and does not show what is currently served. First check whether the names and issuer belong to your services. Investigate unfamiliar issuance with your administrator.

Does HTTPS prove a website is trustworthy?

No. The certificate concerns the connection to a domain name, not the website’s intentions or contents. Even a deceptive name such as example-bank-login.example can have a valid certificate. HTTPS does not make that name the real bank.

Check SSL / TLS on your own domain →