DNS Gurus
Cached · just now
86/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Pennsylvania, L=Pittsburgh, O=Allegheny Health Network, CN=vpn.ahn.org
Issuer
C=US, O=SSL Corporation, CN=Entrust OV TLS Issuing RSA CA 1
Valid From
April 15, 2025
Valid Until
May 14, 2026 124 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8C:27:57:72:7F:DE:93:F5:DF:2D:9F:54:ED:F5:F8:8D:E2:68:60:43:FE:75:04:D2:5D:DF:83:63:78:DD:78:8B
Alternative Names
5 domains

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; script-src; img-src; +1 more
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Strengthen CSP by removing 'unsafe-eval'
  • • 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
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