DNS Gurus
Cached · just now
85/100 SECURITY SCORE

Certificate Information

Subject
CN=*.tenable.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
October 29, 2025
Valid Until
November 27, 2026 329 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D5:44:E3:93:C9:E0:D0:00:74:64:9E:16:B4:05:A7:20:99:4B:AF:73:64:86:3B:52:A8:A4:1D:12:80:CD:10:FB
Alternative Names
4 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
Present
max-age=31536000
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
browsing-topics=()
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Authorized CAs
ssl.com amazon.com pki.goog ; cansignhttpexchanges=yes letsencrypt.org digicert.com
Wildcard CAs
amazon.com digicert.com pki.goog ; cansignhttpexchanges=yes
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • You have authorized 5 CAs - consider limiting to only the CAs you actively use
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts