Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Adobe Fonts (Typekit)
Algolia
BootstrapCDN
Cloudflare
Cloudflare CDN
Cloudflare CDNJS
Cloudflare Web Analytics
Directus
Font Awesome
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Hosted Libraries
Google Search
Google Tag Manager
JotForm
jQuery
jsDelivr
LinkedIn
Netlify
Wistia
YouTube
Certificate Information
Subject
CN=www.mennekes.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
April 13, 2026
Valid Until
July 12, 2026
76 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
97:45:3F:0B:DF:22:33:05:B8:B9:1A:8F:D1:5C:09:9F:D1:AA:8C:7F:81:97:77:E8:C7:30:0F:2B:B7:CF:D0:67
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=31622400; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=*, ambient-light-sensor=*, autoplay=*; +24 more
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