Open
Cached
·
just now
82/100
SECURITY SCORE
Certificate Information
Subject
CN=debugbear.com
Issuer
C=US, O=Google Trust Services, CN=WR3
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
0E:9E:04:E3:BB:9B:E0:A9:AD:49:EB:BC:5F:42:F9:6C:9F:D6:FC:FB:17:7F:C0:30:45:0C:19:83:0E:59:85:76
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=63072000; preload
Content-Security-Policy
Good
report-uri; default-src; script-src; +5 more
report-uri https://www.debugbear.com/_/csp; default-src * 'self'; script-src 'strict-dynamic' 'nonce-a1d6e650-5a61-417b-bbce-1f6404e7808a' 'unsafe-inline' 'self' https: ; style-src * 'self' 'unsafe-inline'; img-src * 'self' data:; object-src 'none'; base-uri 'none'; frame-ancestors 'self'
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
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 X-Content-Type-Options: nosniff
- • 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