Cached · 34m ago
78/100 SECURITY SCORE

Certificate Information

Subject
CN=digg.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
January 06, 2026
Valid Until
February 04, 2027 387 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
47:47:5D:34:AD:78:3A:44:4E:F3:88:F5:7B:3C:7E:4B:F8:DF:A9:16:BB:FC:20:75:F0:79:65:B9:1E:87:78:F5
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
Missing
Not configured
Content-Security-Policy
Missing
Not configured
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
  • Add Content-Security-Policy header to prevent XSS attacks
  • 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
Wildcard CAs
letsencrypt.org pki.goog ; cansignhttpexchanges=yes ssl.com comodoca.com digicert.com ; cansignhttpexchanges=yes
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement
  • You have authorized 7 CAs - consider limiting to only the CAs you actively use
  • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts

Subject Alternative Names

2 domains