DNS Gurus
Cached · 7h ago
83/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Washington, O=F5, Inc., CN=f5.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA OV R40
Valid From
November 06, 2025
Valid Until
December 07, 2026 322 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
27:B3:86:6C:EF:EE:26:AF:7E:79:9C:A7:94:9E:29:81:32:0C:C3:1B:16:9A:74:5D:73:FF:A5:AD:2F:2E:60:25
Alternative Names
8 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
Weak
frame-ancestors
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
Permissions-Policy: geolocation=(), microphone=(), camera=(), gyroscope=(), magnetometer=(), payment=(), fullscreen=(self), autoplay=(self)
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • 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)

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Authorized CAs
amazon.com comodoca.com digicert.com entrust.net letsencrypt.org pki.goog sectigo.com
Incident Reporting
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 'issuewild' records to control wildcard certificate issuance