Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=omalon.com
Issuer
C=US, O=Let's Encrypt, CN=YE1
Valid From
November 01, 2026
Valid Until
January 30, 2027
84 days
Public Key
ECDSA
384 bit
(P-384)
Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
E7:D7:AA:EA:8C:86:CA:6E:AB:B9:58:07:89:91:E9:6F:A0:82:3F:4B:DB:9D:22:DF:66:68:32:A8:F2:A9:B4:F8
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=63072000; includeSubDomains; preload; always;
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=()
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
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