Cached · just now
92/100 SECURITY SCORE

Certificate Information

Subject
CN=cookiebot.eu
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 13, 2025
Valid Until
March 13, 2026 77 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
71:C6:98:15:0E:18:35:AC:03:67:9E:7E:60:98:2D:AB:22:36:E4:85:FA:45:99:89:27:5E:8D:FB:BA:5B:11:FC
Alternative Names

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)
Warnings
  • TLS 1.1 is deprecated and should be disabled
  • TLS 1.0 is deprecated and should be disabled

HTTP Security Headers

Status
Strict-Transport-Security
Excellent
max-age=63072000; includeSubDomains; preload
Content-Security-Policy
Weak
upgrade-insecure-requests
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"), 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
  • Significantly strengthen CSP directives

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

Subject Alternative Names

2 domains