Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
CN=getelevar.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 23, 2025
Valid Until
January 21, 2026
53 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
9C:25:17:E7:FE:08:A5:FC:D9:B1:D2:DC:05:F9:BC:D1:21:8B:DE:0B:87:60:37:AC:77:41:AD:19:C5:FB:BC:90
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=21536000; includeSubdomains
Content-Security-Policy
Good
default-src; frame-ancestors; form-action; +2 more
default-src 'self'; frame-ancestors 'self'; form-action 'self'; upgrade-insecure-requests; frame-ancestors 'none'
X-Frame-Options
Missing
Not configured
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
- • Strengthen CSP by removing 'unsafe-eval'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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