Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
CN=hearstmediact.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
December 29, 2025
Valid Until
March 29, 2026
66 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
07:11:2A:8C:3B:EC:E1:71:7D:57:39:F3:8F:5C:DB:D3:34:4C:02:29:F9:75:D3:47:61:00:60:A8:0F:3D:3D:C1
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
Present
max-age=31536000
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(),midi=(),sync-xhr=(self "https://bookmenow.info" "https://book.mylimobiz.com"),microphone=(self "https://labs.heygen.com"),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self "https://embed.sequel.io"),payment=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
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