Open
Cached
·
just now
93/100
SECURITY SCORE
Certificate Information
Subject
CN=gatekeeperconsent.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 09, 2025
Valid Until
January 07, 2026
37 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
A9:D5:68:31:1D:7F:E7:40:89:C3:0B:E6:FF:D9:58:D2:78:B5:07:69:CE:41:7B:F9:BB:20:9D:11:91:D9:29:F2
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=31536000; includeSubDomains; preload
Content-Security-Policy
Good
default-src; manifest-src; connect-src; +4 more
default-src 'self'; manifest-src 'self'; connect-src 'self' https://*.ezodn.com https://*.ezoic.net; font-src 'self'; img-src data: *; script-src 'self' 'unsafe-inline' https://*.ezodn.com; style-src 'self' 'unsafe-inline' *
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • 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