Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Gravatar
Plyr
YouTube
Microsoft Advertising
Cloudflare
Active incidents
Cloudflare CDN
DigiCert
Facebook
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Static File Front End
Google Tag Manager
HubSpot Forms
jsDelivr
LinkedIn
Sentry
Spotify
Twitter
Usercentrics
Vimeo
XING
Zendesk
Google Cloud
Google Cloud Storage
Certificate Information
Subject
C=DE, L=Bamberg, O=Computop Paygate GmbH, CN=*.computop.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
February 13, 2026
Valid Until
March 16, 2027
322 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
41:97:FC:57:B4:B4:9A:0B:FF:1E:96:D8:D8:26:41:85:20:57:D5:D2:16:2B:47:99:B4:59:D1:DD:DD:FB:BB:AE
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
Good
SAMEORIGIN
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