Open
Cached
·
just now
87/100
SECURITY SCORE
Certificate Information
Subject
CN=clearfly.net
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
November 07, 2025
Valid Until
February 05, 2026
77 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
B2:40:C9:F7:85:2C:E0:04:7D:40:04:E5:09:67:DA:C6:85:87:CE:62:6E:72:16:DD:E7:4E:CD:1B:09:01:08:86
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
Content-Security-Policy
Basic
base-uri; form-action; frame-ancestors; +3 more
base-uri 'self'; form-action 'self'; frame-ancestors 'self'; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval' youtube.com www.youtube.com 'nonce-44UBQW8wWdmXbgN04q8W5g=='
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
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'
- • 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