Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=funnel.travel
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
October 10, 2025
Valid Until
January 08, 2026
48 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
31:6E:2E:D2:52:30:00:AC:87:89:24:C7:ED:4A:25:1F:86:96:0A:E0:C4:A8:86:7E:31:D4:E2:1E:5A:46:D4:89
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
Good
max-age=31536000 ; includeSubDomains
Content-Security-Policy
Good
default-src; script-src; style-src; +5 more
default-src 'self'; script-src 'self' 'unsafe-inline' *.funnel.travel www.gstatic.com *.google.com *.googleapis.com cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' *.funnel.travel www.gstatic.com cdn.jsdelivr.net; font-src 'self' fonts.gstatic.com; frame-src 'self' blob:; frame-ancestors 'none'; img-src 'self' * data:; base-uri 'none'
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • 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