DNS Gurus
Cached · just now
88/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
DigiCert logo DigiCert

Certificate Information

Subject
C=US, ST=Maryland, L=Baltimore, O=SOCIAL SECURITY ADMINISTRATION, CN=ssavpn.ssa.gov
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
June 08, 2026
Valid Until
December 23, 2026 150 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
50:CB:3A:C1:61:B9:6A:22:31:A2:CB:97:6A:70:B4:05:3A:52:09:E5:E6:6D:A6:39:F0:6B:B7:B6:7A:2A:61:4A
Alternative Names
3 domains

Security Configuration

TLS Protocols
TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Basic
default-src; frame-ancestors; base-uri; +1 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Consider adding 'preload' to HSTS for maximum security
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • 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