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:
Unknown Certificate Authority - the server's certificate is not trusted
Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=Illinois, L=North Chicago, O=AbbVie Inc., CN=www.knapsackstudy.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
April 15, 2025
Valid Until
May 16, 2026
115 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C4:02:22:E4:CA:A8:E4:F5:41:A7:AF:72:D9:6C:16:E6:A9:47:92:9E:66:6C:B3:17:02:D4:00:D4:E4:FE:E7:5A
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
Basic
default-src; connect-src; font-src; +7 more
default-src 'self'; connect-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' *.onetrust.com *.cookielaw.org *.maxmind.com *.googleapis.com *.unpkg.com unpkg.com *.facebook.com *.google-analytics.com *.google.com *.youtube.com noembed.com *.fontawesome.com *.plyr.io *.amazonaws.com *.gnosis.earth *.posthog.com *.doubleclick.net; font-src 'self' 'unsafe-inline' data: *.onetrust.com *.typekit.net *.gstatic.com *.fontawesome.com *.cloudflare.com *.plyr.io; img-src 'self' 'unsafe-inline' data: *.cookielaw.org *.google-analytics.com *.googletagmanager.com *.amazonaws.com *.posthog.com *.google.com *.youtube.com *.ytimg.com *.qdsolutions.com *.fastly.net *.googleapis.com *.gstatic.com blob:; frame-src 'self' *.youtube.com google.com *.google.com *.gstatic.com *.googletagmanager.com *.doubleclick.net; script-src 'self' 'unsafe-inline' 'unsafe-eval' 'wasm-unsafe-eval' *.onetrust.com *.cookielaw.org *.maxmind.com *.posthog.com *.jquery.com *.googleapis.com *.facebook.com *.googletagmanager.com *.google-analytics.com *.youtube.com *.fontawesome.com *.plyr.io *.tailwindcss.com *.fastly.net google.com *.google.com *.gstatic.com *.doubleclick.net; style-src 'self' 'unsafe-inline' *.onetrust.com *.googleapis.com *.google.com *.cloudflare.com *.typekit.net *.fontawesome.com *.doubleclick.net *.googleapis.com *.plyr.io *.tailwindcss.com; object-src 'self' 'unsafe-inline' *.googleapis.com *.google.com *.youtube.com *.facebook.com *.posthog.com *.googletagmanager.com *.google-analytics.com *.google.com use.typekit.net *.doubleclick.net; media-src 'self' *.plyr.io *.posthog.com blob:; base-uri 'self';
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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