Open
Cached
·
just now
94/100
SECURITY SCORE
Detected Technologies
PayPal
Gravatar
Google Trust
Auth0
Chameleon
Google Tag Manager
Fullstory
WordPress
Liveblocks
HubSpot Forms
Cookiebot
HubSpot Feedback & Surveys
Google DoubleClick
Google Analytics
Google Conversion Tracking
ClearBit
Dropbox
Mixpanel
Segment
Datadog
Active incidents
Google Cloud Storage
Google Static File Front End
Google Fonts
Wistia
Svix
Transcend
Loom
LinkedIn
Stripe
HubSpot Analytics
Google Search
Ketch
Facebook
OneTrust
Adobe Fonts (Typekit)
Split.io
Vimeo
TrustArc
Statsig
HubSpot
Intercom
YouTube
HubSpot Live Chat
Sentry
Google Cloud
Certificate Information
Subject
CN=trust.obsidiansecurity.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 15, 2026
Valid Until
June 13, 2026
43 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
8A:7B:EC:73:71:BE:85:02:31:BB:03:AD:FE:C7:E3:81:04:4A:F6:AD:B0:17:EE:27:2D:A7:07:A0:FB:EA:C6:0A
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
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
no-referrer,strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=(); +13 more
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Strengthen CSP by removing 'unsafe-eval'
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