Open
Cached
·
just now
80/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
UNKNOWN={:asn1_OPENTYPE, <<19, 2, 85, 83>>}, UNKNOWN={:asn1_OPENTYPE, <<12, 17, 71, 111, 118, 101, 114, 110, 109, 101, 110, 116, 32, 69, 110, 116, 105, 116, 121>>}, UNKNOWN=Government Entity, C=US, ST=Maryland, L=Baltimore, O=Social Security Administration, CN=www.ssa.gov
Issuer
C=US, O=DigiCert Inc, CN=DigiCert EV RSA CA G2
Valid From
September 24, 2025
Valid Until
October 20, 2026
88 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
66:C8:F6:C6:C1:19:CF:08:87:63:25:DB:EA:DA:FB:F9:CC:4C:5C:91:DA:AC:0B:49:71:AB:4D:F4:B7:59:AF:DE
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
Excellent
max-age=31536000 ; includeSubDomains ; preload
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 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
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