B score 79 / 100ok, weaknesses worth fixing

Run 23 2026-11-06 19:55 UTC 57 checks profile 5 0.4 s

example.com

Share
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
CAA Legacy Suites ECH Redirect HSTS CSP XFO XCTO Referrer Perms COOP Leakage Caching DMARC
DNS A TLS A HTTP F EMAIL C IP A+
Run 232026-11-06grade B

Run 23 · 2026-11-06 · grade B
latest run

Tap a line for its history. Step back with ‹ to replay a run.

11-0610-28

Each line carries its trace: 23 runs, newest on top.

hover a run to replay the spectrum · tap to pin

Show history as a table
  • pass
  • warn
  • fail
  • fixed since run 22
57 checks · line height = weight in the grade

Since run 22

2026-11-06 · grade B → B

  • removed tls.probes@104.20.23.154:443 removed · tls tls
  • added tls.probes@172.66.147.243:443 added · tls tls

15 lines need attention

3 fail · 12 warn

Your web server configuration

12 lines
fail TLS·25

fail · TLS·25 · in all 23 runs

Legacy protocol versions

in all 23 runs

172.66.147.243: accepts TLS 1.0, TLS 1.1

Fix: Disable SSLv3, TLS 1.0 and TLS 1.1 and allow only TLS 1.2 and TLS 1.3.

TLS · RFC 8996evidence →guide →

fail HTTP·34

fail · HTTP·34 · in all 23 runs

HTTPS redirect

in all 23 runs

HTTP port 80 does not redirect to HTTPS

Fix: Serve HTTP on port 80 and redirect every request to HTTPS with a 301 before serving content.

HTTP · RFC 9110evidence →guide →

fail HTTP·35

fail · HTTP·35 · in all 23 runs

HSTS

in all 23 runs

No HSTS header found

Fix: Send Strict-Transport-Security with max-age=31536000 on all HTTPS responses.

HTTP · RFC 6797evidence →guide →

warn TLS·26

warn · TLS·26 · in all 23 runs

Weak cipher suites

in all 23 runs

172.66.147.243: accepts CBC suite TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA; 172.66.147.243: accepts static RSA suite TLS_RSA_WITH_AES_128_GCM_SHA256

Fix: Allow only ECDHE suites with AES-GCM or ChaCha20-Poly1305 for TLS 1.2, and remove RC4, 3DES, DES, export, NULL, anonymous, CBC and static RSA suites.

TLS · RFC 9325evidence →guide →

warn HTTP·38

warn · HTTP·38 · in all 23 runs

Content Security Policy

in all 23 runs

No Content-Security-Policy header

Fix: Send an enforced Content-Security-Policy with default-src, object-src 'none' and base-uri that restricts scripts to trusted origins.

HTTP · W3C Content Security Policy Level 3evidence →guide →

warn HTTP·39

warn · HTTP·39 · in all 23 runs

X-Frame-Options

in all 23 runs

Missing x-frame-options header

Fix: Send X-Frame-Options: DENY, or SAMEORIGIN where the site frames its own pages.

HTTP · RFC 7034evidence →guide →

warn HTTP·40

warn · HTTP·40 · in all 23 runs

X-Content-Type-Options

in all 23 runs

Missing x-content-type-options header

Fix: Send X-Content-Type-Options: nosniff on all responses.

HTTP · WHATWG Fetch Standardevidence →guide →

warn HTTP·41

warn · HTTP·41 · in all 23 runs

Referrer-Policy

in all 23 runs

Missing referrer-policy header

Fix: Send Referrer-Policy: strict-origin-when-cross-origin or stricter.

HTTP · W3C Referrer Policyevidence →guide →

warn HTTP·42

warn · HTTP·42 · in all 23 runs

Permissions-Policy

in all 23 runs

Missing permissions-policy header

Fix: Send a Permissions-Policy that disables the browser features the site does not use.

HTTP · W3C Permissions Policyevidence →guide →

warn HTTP·43

warn · HTTP·43 · in all 23 runs

Cross-Origin-Opener-Policy

in all 23 runs

Missing cross-origin-opener-policy header

Fix: Send Cross-Origin-Opener-Policy: same-origin, or same-origin-allow-popups when the site relies on popups such as payment or login windows.

HTTP · HTML Living Standardevidence →guide →

warn HTTP·45

warn · HTTP·45 · in all 23 runs

Information leakage

in all 23 runs

Info leakage headers: Server

Fix: Remove the Server, X-Powered-By and similar technology headers from the server's responses.

HTTP · RFC 9110evidence →guide →

warn HTTP·46

warn · HTTP·46 · in all 23 runs

Cache control

in all 23 runs

No Cache-Control header

Fix: Send an explicit Cache-Control header on each response and pair max-age=0 with no-cache or must-revalidate.

HTTP · RFC 9111evidence →guide →

Your DNS provider

3 lines
warn DNS·04

warn · DNS·04 · in all 23 runs

CAA records

in all 23 runs

No CAA records found: any Certificate Authority can issue certificates for this domain; cf. RFC 8659

Fix: Publish issue and issuewild CAA records naming the allowed certificate authorities, using only known tags.

DNS · RFC 8659evidence →guide →

warn MAIL·50

warn · MAIL·50 · in all 23 runs

DMARC

in all 23 runs

no aggregate reports

Fix: Publish one DMARC record with p=reject, without sp=none or pct=0, and with an rua address authorised to receive reports.

Email · RFC 7489evidence →guide →

warn TLS·33

warn · TLS·33 · in all 23 runs

ECH advertised

in all 23 runs

172.66.147.243: ECH not advertised in HTTPS DNS record; 104.20.23.154: ECH not advertised in HTTPS DNS record

Fix: Publish the server's ECH configuration in the ech= parameter of the HTTPS record, once Encrypted Client Hello is enabled on the server.

TLS · draft-ietf-tls-esnievidence →guide →

Evidence

recorded with this run

Key records · 10 record types answered

TypeDataTTL
A104.20.23.154300
A172.66.147.243300
AAAA2606:4700:10::6814:179a300
AAAA2606:4700:10::ac42:93f3300
NSelliott.ns.cloudflare.com.21600
NShera.ns.cloudflare.com.21600
CAAno records
DS2371 13 2 C988EC423E3880EB8DD8A46FE06CA230EE23F35B578D64E78B29C…15912

← swipe the table

Certificate chain · port 443 · 2 addresses, consistent

#SubjectIssuerKeyNot after
0example.comCloudflare TLS Issuing ECC CA 3ECDSA P-2562026-12-25
1Cloudflare TLS Issuing ECC CA 3SSL.com TLS Transit ECC CA R2ECDSA P-2562035-05-27
2SSL.com TLS Transit ECC CA R2SSL.com TLS ECC Root CA 2022ECDSA P-3842037-10-17
3SSL.com TLS ECC Root CA 2022AAA Certificate ServicesECDSA P-3842028-12-31

← swipe the table

Response · 200 · h2 · https://example.com/

HeaderValue
strict-transport-securitynot sent
content-security-policynot sent
x-frame-optionsnot sent
x-content-type-optionsnot sent
referrer-policynot sent
permissions-policynot sent

← swipe the table

Mail records · 1 MX host

RecordValue
MX0 .
SPFv=spf1 -all
DMARCv=DMARC1;p=reject;sp=reject;adkim=s;aspf=s
DKIMdefault: revoked

← swipe the table

Addresses · 4 addresses

AddressASNOrgCountryNetworkListed
104.20.23.154AS13335Cloudflare, Inc.cloudnone
172.66.147.243AS13335Cloudflare, Inc.cloudnone
2606:4700:10::6814:179aAS13335Cloudflare, Inc.cloudnone
2606:4700:10::ac42:93f3AS13335Cloudflare, Inc.cloudnone

← swipe the table

This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com.

42 lines clean · checks that passshow
pass DNS·01

pass · DNS·01

DNSSEC signed

The zone publishes DNSKEY records with a key-signing key, anchored by matching DS records at its parent. If it failed: Resolvers cannot detect forged or tampered answers for the domain.

DNS · RFC 4033evidence →guide →

pass DNS·02

pass · DNS·02

DNSKEY algorithm

None of the zone's DNSKEY records uses RSAMD5, DSA or an RSASHA1 algorithm. If it failed: Weak or deprecated algorithms are unsupported by validators or no longer considered safe.

DNS · RFC 8624evidence →guide →

pass DNS·03

pass · DNS·03

DNSSEC key rollover

The zone has a single key-signing key with a DS record at its parent, and every DS record matches one of its DNSKEY records. If it failed: A broken rollover can make validating resolvers reject every answer for the domain.

DNS · RFC 7583evidence →guide →

pass DNS·05

pass · DNS·05

Nameserver redundancy

The zone lists at least two distinct nameservers in its NS records. If it failed: With a single nameserver, its outage takes the whole domain offline.

DNS · RFC 2182evidence →guide →

pass DNS·06

pass · DNS·06

Lame delegation

Every nameserver that answered the SOA query answered authoritatively for the zone. If it failed: Resolvers that pick the lame nameserver fail or time out, causing intermittent resolution errors.

DNS · RFC 1912evidence →guide →

pass DNS·07

pass · DNS·07

Delegation consistency

The NS set a recursive resolver returns matches the NS set the zone's own nameservers return. If it failed: Resolvers see different nameserver sets depending on which server they ask, which leads to inconsistent or failing resolution.

DNS · RFC 1034evidence →guide →

pass DNS·08

pass · DNS·08

No CNAME at apex

Where the checked name is a zone apex, it holds no CNAME record. If it failed: A CNAME at the apex conflicts with the SOA and NS records and breaks mail and other records.

DNS · RFC 1034evidence →guide →

pass DNS·09

pass · DNS·09

HTTPS record

The domain publishes HTTPS or SVCB records that keep alias and service mode apart and hold at most one alias record. If it failed: Clients cannot reliably learn HTTP/2, HTTP/3 or ECH support before connecting, which costs round trips.

DNS · RFC 9460evidence →guide →

pass DNS·10

pass · DNS·10

TTL range

No record has a nonzero TTL below 60 seconds, no NS or MX record has one above a week, and the SOA minimum is at most a day. If it failed: Very low TTLs load resolvers, while very high NS, MX or negative-caching TTLs delay the propagation of changes.

DNS · RFC 1912evidence →guide →

pass TLS·11

pass · TLS·11

TLS reachable

At least one address of the domain completes a TLS handshake on the inspected port. If it failed: Visitors cannot reach the site over HTTPS at all.

TLS · RFC 8446evidence →guide →

pass TLS·12

pass · TLS·12

Chain trusted

The served certificate chain verifies to a trusted root certificate. If it failed: Browsers show a security warning and block the site.

TLS · RFC 5280evidence →guide →

pass TLS·13

pass · TLS·13

Certificate valid

Every certificate in the served chain is within its validity period. If it failed: Browsers block access to the site until the certificate is replaced.

TLS · RFC 5280evidence →guide →

pass TLS·14

pass · TLS·14

Hostname match

The certificate's Subject Alternative Names cover the hostname. If it failed: Browsers reject the connection with a name mismatch error.

TLS · RFC 9525evidence →guide →

pass TLS·15

pass · TLS·15

Chain complete

The served chain is in issuing order and needs no missing intermediate to reach its root. If it failed: Clients that do not reorder the chain or fetch missing intermediates fail to validate the certificate.

TLS · RFC 8446evidence →guide →

pass TLS·16

pass · TLS·16

Strong signature

No certificate in the served chain below the root is signed with SHA-1, MD5 or MD2. If it failed: Weak signatures can be forged and are rejected by modern browsers.

TLS · CA/Browser Forum Baseline Requirementsevidence →guide →

pass TLS·17

pass · TLS·17

Key strength

No certificate in the chain has an RSA key below 2048 bits or an ECDSA key below 256 bits. If it failed: Short keys can be broken and are refused by modern clients.

TLS · CA/Browser Forum Baseline Requirementsevidence →guide →

pass TLS·18

pass · TLS·18

Expiry window

No certificate in the chain expires within the next 30 days. If it failed: Without renewal, browsers start blocking the site when it expires.

TLS · RFC 5280evidence →guide →

pass TLS·19

pass · TLS·19

Certificate lifetime

The leaf certificate's validity period is at most 398 days, the browser maximum. If it failed: Major browsers reject publicly-trusted certificates issued with a longer lifetime.

TLS · CA/Browser Forum Baseline Requirementsevidence →guide →

pass TLS·20

pass · TLS·20

SAN quality

The leaf certificate lists fewer than 100 Subject Alternative Names, none of them a single-label name or a private IPv4 address. If it failed: Internal names disclose private infrastructure, and very large SAN lists share one key across many sites.

TLS · RFC 9525evidence →guide →

pass TLS·22

pass · TLS·22

TLS version

The server negotiates TLS 1.3. If it failed: TLS 1.2 lacks the encrypted handshake and fixed safe cipher suites of TLS 1.3 and stays safe only with careful configuration.

TLS · RFC 8446evidence →guide →

pass TLS·23

pass · TLS·23

Forward secrecy

The negotiated cipher suite uses an ephemeral key exchange, so past sessions stay safe if the key is later compromised. If it failed: A later compromise of the private key exposes recorded past sessions.

TLS · RFC 9325evidence →guide →

pass TLS·24

pass · TLS·24

AEAD cipher

The negotiated cipher suite provides authenticated encryption (AEAD), such as AES-GCM or ChaCha20-Poly1305. If it failed: Legacy cipher modes are vulnerable to padding-oracle and related attacks.

TLS · RFC 9325evidence →guide →

pass TLS·27

pass · TLS·27

OCSP stapling

The server staples an OCSP response to the handshake, sparing clients a separate revocation lookup. If it failed: Clients must contact the CA to check revocation, which costs latency and leaks browsing.

TLS · RFC 6066evidence →guide →

pass TLS·28

pass · TLS·28

CT logged

The certificate embeds at least two Signed Certificate Timestamps from Certificate Transparency logs. If it failed: Browsers that enforce a Certificate Transparency policy may reject certificates with too few SCTs.

TLS · RFC 6962evidence →guide →

pass TLS·29

pass · TLS·29

CAA compliant

No CAA record of the domain forbids the certificate authority that issued the certificate. If it failed: Issuance outside the CAA policy points to mis-issuance or a stale policy, and an unknown critical tag forbids every CA from issuing.

TLS · RFC 8659evidence →guide →

pass TLS·31

pass · TLS·31

Multi-IP consistency

Every address of the domain serves the same leaf certificate, TLS version and cipher suite. If it failed: Visitors get different security depending on which address they reach.

TLS · RFC 9325evidence →guide →

pass TLS·32

pass · TLS·32

ALPN consistency

Every address of the domain negotiates the same ALPN protocol. If it failed: Clients see HTTP/2 on some connections and not on others, which makes behaviour unpredictable.

TLS · RFC 7301evidence →guide →

pass HTTP·36

pass · HTTP·36

CORS policy

The CORS probe from a foreign origin got neither a wildcard Access-Control-Allow-Origin nor its origin reflected with credentials allowed. If it failed: Other sites can read responses, in the reflected case with the visitor's credentials.

HTTP · WHATWG Fetch Standardevidence →guide →

pass HTTP·44

pass · HTTP·44

Deprecated headers

Responses carry none of the deprecated security headers X-XSS-Protection, Expect-CT and Public-Key-Pins. If it failed: Deprecated headers have no protective effect and some reintroduce vulnerabilities in old browsers.

HTTP · OWASP Secure Headers Projectevidence →guide →

pass MAIL·48

pass · MAIL·48

SPF

The domain publishes a single SPF record within the DNS lookup limits, with no +all, ?all or ptr mechanism. If it failed: Others can send mail in the domain's name, and legitimate mail may be rejected. domain declares it sends no mail (Null MX or SPF -all only)

Email · RFC 7208evidence →guide →

pass IP·57

pass · IP·57

IP reputation

None of the domain's checked addresses is listed by Spamhaus or flagged as a Tor exit, command-and-control host or VPN endpoint. If it failed: Flagged addresses are blocked or throttled by mail receivers, firewalls and CDNs.

IP · RFC 5782evidence →guide →

untested TLS·21

untested · TLS·21

AIA reachable

TLS · RFC 5280

untested TLS·30

untested · TLS·30

DANE valid

TLS · RFC 6698

untested HTTP·37

untested · HTTP·37

Secure cookies

HTTP · RFC 6265

untested MAIL·47

untested · MAIL·47

MX records

Email · RFC 5321

untested MAIL·49

untested · MAIL·49

DKIM

Email · RFC 6376

untested MAIL·51

untested · MAIL·51

MTA-STS

Email · RFC 8461

untested MAIL·52

untested · MAIL·52

TLS-RPT

Email · RFC 8460

untested MAIL·53

untested · MAIL·53

BIMI

Email · draft-brand-indicators-for-message-identification

untested MAIL·54

untested · MAIL·54

SMTP DANE

Email · RFC 7672

untested MAIL·55

untested · MAIL·55

DNS blocklists

Email · RFC 5782

untested MAIL·56

untested · MAIL·56

Forward-confirmed rDNS

Email · RFC 1912

Result page

The grade, the spectrum, the open issues and the evidence of the latest run of this domain. Copy or download the stored run from the Evidence section.

Keyboard

rCheck again
j / kNext or previous open issue
?Open this help
EscClose this help

How the grade is scored →