DNS Gurus
Cached · just now
80/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
Let's Encrypt logo Let's Encrypt

Certificate Information

Subject
CN=quantcast.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
May 28, 2026
Valid Until
August 26, 2026 87 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A9:06:C9:90:67:CA:CD:92:C2:71:5D:3A:C0:29:31:DB:94:81:77:1B:E7:B0:17:6B:4B:F8:31:AA:F2:C1:37:55
Alternative Names
28 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
frame-ancestors Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
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
amazon.com digicert.com letsencrypt.org
Incident Reporting
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • Consider adding 'issuewild' records to control wildcard certificate issuance