DNS Gurus
Open Cached · 2h ago
80/100 SECURITY SCORE

Certificate Information

Subject
CN=*.www.fandom.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
September 27, 2025
Valid Until
December 26, 2025 49 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F6:06:06:68:3B:A8:6A:52:D2:52:FB:D9:C5:72:57:29:3B:92:23:AF:4C:25:55:74:F7:FD:A3:A5:21:89:12:E8
Alternative Names
23 domains

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Weak
upgrade-insecure-requests
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Significantly strengthen CSP directives
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • Add X-Content-Type-Options: nosniff
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Authorized CAs
amazontrust.com awstrust.com certainly.com digicert.com globalsign.com letsencrypt.org amazon.com amazonaws.com
Incident Reporting
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • You have authorized 8 CAs - consider limiting to only the CAs you actively use
  • • Consider adding 'issuewild' records to control wildcard certificate issuance