Open Cached · just now
92/100 SECURITY SCORE

Certificate Information

Subject
CN=usatoday.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
November 26, 2025
Valid Until
February 24, 2026 84 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D9:6D:B9:C5:EA:6C:9B:50:20:E7:5F:A1:54:98:92:EC:2F:F0:58:07:EA:8F:B7:7F:05:A4:1A:AA:75:6D:B7:92
Alternative Names

Security Configuration

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

HTTP Security Headers

Status
Strict-Transport-Security
Excellent
max-age=63072000;includeSubDomains;preload
Content-Security-Policy
Weak
upgrade-insecure-requests; frame-ancestors; object-src
X-Frame-Options
Excellent
deny
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
bluetooth=(),camera=(),clipboard-read=(),display-capture=(),geolocation=(),local-fonts=(),local-network-access=(),microphone=(),otp-credentials=(),payment=(),serial=(),usb=(),window-management=(),xr-spatial-tracking=()
Recommendations
  • Significantly strengthen CSP directives

CAA Records (Certificate Authority Authorization)

CAA Records
Not Configured (Any CA can issue certificates)
CAA Issues
  • No CAA records configured - any CA can issue certificates
Recommendations
  • Implement CAA records to restrict which CAs can issue certificates for your domain
  • This adds an extra layer of security against unauthorized certificate issuance
  • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
  • Consider adding 'iodef' record to receive security incident reports