SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Invalid Certificate - the server's certificate is malformed or invalid
Open
Cached
·
just now
84/100
SECURITY SCORE
Certificate Information
Subject
CN=sni-support-required-for-valid-ssl
Issuer
CN=sni-support-required-for-valid-ssl
Valid From
August 06, 2025
Valid Until
August 04, 2035
3487 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A7:D8:ED:F4:BA:1A:10:A6:D5:2B:EC:81:8A:3F:CA:57:FB:5A:EA:E7:ED:AB:AF:4E:EF:B0:0F:41:FD:4E:6F:F7
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Weak
max-age= 63072000; includeSubdomains; preload
Content-Security-Policy
Basic
font-src; style-src; script-src; +6 more
font-src 'self' 'unsafe-inline' fonts.gstatic.com use.typekit.net *.datocms.com data:; style-src 'self' *.datocms.com 'unsafe-inline' fonts.googleapis.com; script-src 'self' maps.googleapis.com iframe.ly vimeo.com *.datocms.com 'sha256-wTmDOOsjiIkwlxpJL+fmZiEljPmod4V3/szERINsuQ0=' 'sha256-tJ+4LtAXQN7vM9KbVVDBBCmQtUWAzy2yhs3MaaRE8K4=' 'sha256-c1m3OFbRZFklSX1yc2tWaOwzKLnIrZ+LkwTAS6yplms=' 'unsafe-eval'; object-src 'none'; worker-src blob:; form-action 'self'; frame-ancestors 'self'; report-uri https://hj3dt24nbqsh52wnycrxoqdcme0edlxf.lambda-url.us-east-1.on.aws/; report-to csp-reports
X-Frame-Options
Excellent
DENY
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
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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