Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
YouTube
Ahrefs
Calendly
Cloudflare CDNJS
Cookiebot
G2
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
Intercom
jsDelivr
Leadfeeder
LinkedIn
Mixpanel
PartnerStack
ShareThis
Storylane
Webflow
Certificate Information
Subject
CN=survicate-cdn.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 10, 2026
Valid Until
June 08, 2026
77 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
99:F7:47:3A:8F:FB:97:22:39:0A:E4:7C:04:DD:11:F2:3F:C0:82:86:11:94:E8:81:B5:3F:7B:3D:D7:46:4E:20
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
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • 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