Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Google Trust
Adobe Target
AWS CloudFront
YouTube
Google Tag Manager
Bing
G2
Salesforce Cloud
AppNexus (Xandr)
HubSpot Forms
Google DoubleClick
Google Analytics
Crazy Egg
Cloudflare CDN
Greenhouse
Google Static File Front End
Google API JS Client
Google Fonts
Wistia
Twitter
LinkedIn
Adobe Experience Cloud
Drift
unpkg
Cvent
Turtl
Google Search
Cloudflare
Adobe Marketo
Adobe Dynamic Tag Management
Qualified
OneTrust
Salesforce Sites
AWS
Oracle Eloqua
jQuery
Akamai
Google Cloud
Certificate Information
Subject
CN=geolocation.onetrust.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 26, 2026
Valid Until
April 26, 2026
65 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
B9:75:F0:95:C8:7F:CD:61:C6:1E:80:44:33:6D:64:D3:02:CF:9C:AB:37:88:EC:00:F5:01:55:88:23:BD:0B:52
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=31536000; includeSubDomains; preload
X-Frame-Options
Present
SAMEORIGIN, SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • 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