Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Google Trust
Google AdSense
Google Tag Manager
G2
Amplitude
Kinsta
XING
Reddit
Active incidents
HubSpot Forms
Cookiebot
Megaphone
Google DoubleClick
Google Analytics
Microsoft Advertising
ClearBit
Greenhouse
Outbrain
Oktopost
Google API JS Client
Leadfeeder
Hotjar
LinkedIn
Contentsquare
HubSpot Analytics
Google Search
Demandbase
Facebook
Matomo
HubSpot
Microsoft Clarity
HubSpot Live Chat
Sentry
Certificate Information
Subject
CN=sosafe.de
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 27, 2026
Valid Until
July 26, 2026
76 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
5D:A6:8C:5A:A4:A7:99:E8:85:B4:4B:41:6D:9A:D4:D3:BB:B7:E0:4E:62:FD:9C:8A:74:AA:71:A2:30:D1:C9:CD
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
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
payment=(self), geolocation=(self), microphone=(self); +6 more
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
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