Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Adobe Fonts (Typekit)
Azure Blob Storage
Bing
Facebook
Font Awesome
GitHub
Active incidents
Google API JS Client
Google DoubleClick
Google Search
Google Tag Manager
HubSpot
Active incidents
HubSpot Forms
Active incidents
jsDelivr
LinkedIn
Microsoft Clarity
Mutiny
OneTrust
Optimizely
Reddit
Sanity
6sense
Wistia
Certificate Information
Subject
CN=getdbt.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 21, 2026
Valid Until
July 20, 2026
81 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
88:EC:A4:1E:85:1C:45:1F:29:EA:B0:90:A1:88:AE:68:4E:B6:DF:42:45:ED:67:8C:D1:9A:97:F5:FD:38:3C: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
Excellent
max-age=63072000; includeSubDomains; preload
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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