Open
Cached
·
4h ago
93/100
SECURITY SCORE
Certificate Information
Subject
CN=usercentrics.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 21, 2025
Valid Until
March 21, 2026
67 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
0C:50:01:E9:4A:3D:24:94:E1:72:49:F7:BA:F9:04:20:8F:99:CE:CA:FD:22:74:A8:1F:DA:79:6D:EF:30:01:00
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
Content-Security-Policy
Basic
default-src; frame-src
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
accelerometer=(self), autoplay=(self "https://www.youtube.com"), camera=(self), display-capture=(self), encrypted-media=(self), fullscreen=(self "https://www.youtube.com" "https://app.storylane.io"), geolocation=(self), gyroscope=(self), magnetometer=(self), microphone=(self), midi=(self), payment=(self), picture-in-picture=(self "https://www.youtube.com"), publickey-credentials-get=(self), sync-xhr=(self), usb=(self), screen-wake-lock=(self), xr-spatial-tracking=(self)
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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