mozilla.org

Scanned 9 days ago · Aug 11, 2026, 9:22 PM

A-

TLS & Certificate

Protocol support, cipher strength and the certificate chain, evaluated the way a browser would.

Score85%
  • the server accepts 2 weak cipher suite(s): AES256-GCM-SHA384, AES128-GCM-SHA256
  • the HSTS max-age is shorter than 6 months
NegotiatedTLSv1.3, TLS_AES_256_GCM_SHA384
Forward secrecyYes
HSTSenabled, max-age=60

Protocol support

YesTLS 1.3
YesTLS 1.2
NoTLS 1.1 (deprecated)
NoTLS 1.0 (deprecated)

Cipher suites probed

Each suite below was tested with its own TLS 1.2 handshake, restricted to exactly that cipher - “accepted” means the server completed a handshake using it, not merely that it's listed as a possibility.

ECDHE-ECDSA-AES256-GCM-SHA384
SecureNot offered
ECDHE-RSA-AES256-GCM-SHA384
SecureAccepted
ECDHE-ECDSA-AES128-GCM-SHA256
SecureNot offered
ECDHE-RSA-AES128-GCM-SHA256
SecureAccepted
ECDHE-ECDSA-CHACHA20-POLY1305
SecureNot offered
ECDHE-RSA-CHACHA20-POLY1305
SecureAccepted
DHE-RSA-AES256-GCM-SHA384
SecureNot offered
DHE-RSA-AES128-GCM-SHA256
SecureNot offered
ECDHE-RSA-AES256-SHA384
WeakNot offered
ECDHE-RSA-AES128-SHA256
WeakNot offered
AES256-GCM-SHA384
WeakAccepted
AES128-GCM-SHA256
WeakAccepted
DES-CBC3-SHA
InsecureNot offered
RC4-SHA
InsecureNot offered
NULL-SHA
InsecureNot offered

Certificate

Subjectmozilla.org
IssuerWR3
Additional namesmozilla.org
ValidJul 23, 2026, 4:01 PM – Oct 21, 2026, 4:55 PM (expires in 71 days)
KeyRSA 2048 bit
Certificate chain3 certificate(s)
Trusted by common trust storesYes
Matches the scanned hostnameYes
Self-signedNo
D

Security Headers

The HTTP response headers browsers use to restrict what a page - or an attacker inside it - can do.

Score50%
  • no Content-Security-Policy header
  • no clickjacking protection (X-Frame-Options or frame-ancestors)
  • no Permissions-Policy header
  • no Cross-Origin-Resource-Policy header
  • the Server header discloses "granian"
Content-Security-Policynot set
Strict-Transport-Securitymax-age=31536000
X-Content-Type-Optionsnosniff
X-Frame-Optionsnot set
Referrer-Policystrict-origin-when-cross-origin
Permissions-Policynot set
Cross-Origin-Opener-Policysame-origin
Cross-Origin-Resource-Policynot set
A+

Email

Whether mail delivered to this domain is protected in transit, and whether SPF/DMARC stop it being spoofed.

Score100%
  • port 25 was not reachable on any mail server from our scanner (commonly blocked by cloud providers) - mail transport security could not be verified
SPFv=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:_spf.mozilla.com include:_spf.google.com include:spf.fundraiseup.com ~all
DMARCv=DMARC1; p=reject; pct=100; adkim=r; aspf=r; rua=mailto:[email protected],mailto:[email protected]

Mail servers

aspmx.l.google.comnot reachable on port 25 from our scanner
alt1.aspmx.l.google.comnot reachable on port 25 from our scanner
alt2.aspmx.l.google.comnot reachable on port 25 from our scanner