Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
CN=untilgone.com
Issuer
C=US, O=DigiCert, Inc., CN=Encryption Everywhere G3 TLS ECC P384 SHA384 2023 CA1
Valid From
December 26, 2025
Valid Until
December 25, 2026
346 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
F2:F1:17:BF:97:49:CB:83:C6:1C:B2:BA:C3:80:72:BF:FC:7C:2D:F6:7D:40:B8:BF:33:B6:C4:55:33:E8:4D:62
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
Weak
max-age=0
Content-Security-Policy
Weak
block-all-mixed-content; frame-ancestors; upgrade-insecure-requests
X-Frame-Options
Present
allow-from https://untilgone-com.cdn.ampproject.org
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
- • Significantly strengthen CSP directives
- • 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