CheckSSL.dev
Tools

Illustrative example

SSL & TLS example report

Warning

demo.example

This is a permanent example with fictional data for demo.example. No scan runs when you open this page. Dates, timings and results are illustrative.

A verified TLS connection has 21 days left on its certificate at the example’s fixed reference time. One protocol probe and the CRL check remain unknown.

What to do next: Check renewal and deployment before expiry. Investigate unavailable protocol and revocation checks separately; a connection score does not answer them.

Check TLS How this tool works

Trusted connection

TLS connection and hostname verified.

Expires: 17 Nov 2026 12:00:00 UTC · 21 days remaining

Basic connection score: 90 / 100

This score covers trust, hostname and expiry only. Protocol support, revocation, key strength and Certificate Transparency are reported separately below.

Certificate

Common name
demo.example
Certificate type
Domain Validation · Multi-domain
Issuer
Illustrative Certificate Authority · Example Intermediate CA
Valid from
19 Aug 2026 12:00:00 UTC
Valid until
17 Nov 2026 12:00:00 UTC
Validity duration
90 days
Signature algorithm
sha256WithRSAEncryption
Public key
RSA · 2048 bits
Serial number
01A2B3C4
SHA-256 fingerprint
779b344296da1f642519ffa0f991b148c33340fb053fcaee2552103f1cf39525

Subject Alternative Names (SAN)

Total DNS / IP SAN count: 2

  • DNS:demo.example
  • DNS:www.demo.example

Connection

Negotiated TLS version
TLSv1.3
Negotiated cipher
TLS_AES_128_GCM_SHA256 · 128 bits
Connected IP · port 443
192.0.2.10
Duration
42.6 ms

Supported TLS versions

TLSv1.3
Supported
TLSv1.2
Supported
TLSv1.1
Rejected by server
TLSv1.0
Unknown / not checked

Each version is tested against the connected IP using separate handshakes. Timeouts and scanner limitations remain unknown. These probes do not verify certificate trust or enumerate every cipher.

DNS CAA

CAA records found at demo.example.

  • 0 issue "ca.demo.example"

CAA discovery follows aliases and parent domains. Records describe issuance policy; issuer authorization and DNSSEC are not verified.

Certificate chain

2 certificates received

Certificates sent by the server, in the order received. The root may be omitted by the server.

Received order: not verified.

The trusted path can end at a different certificate in the local trust store. A cross-signed CA and its self-signed root can share a name and key while having different issuers and expiry dates.

  1. Server certificate

    Subject
    demo.example
    Issued by
    Example Intermediate CA
    Valid from
    19 Aug 2026 12:00:00 UTC
    Valid until
    17 Nov 2026 12:00:00 UTC
  2. Intermediate / cross-signed CA

    Subject
    Example Intermediate CA
    Organization
    Illustrative Certificate Authority
    Issued by
    Example Root CA
    Valid from
    27 Oct 2025 12:00:00 UTC
    Valid until
    27 Oct 2027 12:00:00 UTC

Revocation / issuer URLs

CA Issuers

https://demo.example/example-intermediate.crt

OCSP

No URL available.

CRL

http://demo.example/example-leaf.crl

Findings

How is the basic connection score calculated?
  • Connection and trust50 / 50 points
  • Hostname25 / 25 points
  • Validity period15 / 25 points

Expiry within 30 days earns 15 of 25 validity points. Unknown checks prevent a total score. This is not a full TLS grade or a guarantee of website security. Ruleset: tls-v2.

About this scan

Checks certificate trust, hostname, validity and key details on port 443. New scans also probe TLS 1.0–1.3, discover CAA records and attempt server-certificate revocation verification via CRL, within 20 seconds. Unknown checks remain explicit. Does not verify CT compliance, OCSP or enumerate every cipher.

This fixed example is public and does not expire. It contains fictional data, not a stored visitor scan.

A snapshot, not a security guarantee.

Read the methodology and report data policy