Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=support.privacy.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
March 05, 2026
Valid Until
June 03, 2026
31 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
6C:A3:E3:89:8A:B6:08:24:CD:BF:AE:6F:3D:D7:6C:D7:AF:29:FC:E7:05:FC:A2:98:9D:EA:4D:8D:C7:9C:63:4C
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
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
accelerometer=(), browsing-topics=(), camera=(); +15 more
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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