Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=*.prod.buzzfeed.io
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
April 13, 2025
Valid Until
May 13, 2026
120 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
63:F2:F4:8C:F6:9F:22:9F:9D:90:6A:CC:B2:F7:0A:91:34:BE:7E:25:F9:D7:A6:B0:7F:B3:0E:06:C4:DC:57:D7
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=31536000
Content-Security-Policy
Good
default-src; style-src; img-src
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
Same-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • Consider adding Permissions-Policy to control browser features
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
Subject Alternative Names
14 domains
*.buzzfeed.com
*.buzzfeed.io
*.glb.buzzfeed.io
*.prod.buzzfeed.io
*.sso.prod.buzzfeed.io
*.bzfd.it
*.huffingtonpost.com
*.cambria-production.huffpo.net
*.cambria-staging.huffpo.net
*.use1.huffpo.net
*.huffpost.net
*.prod.huffpost.net
*.sso.prod.huffpost.net
*.tools.huffpost.net
Other domains in certificate