Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Bing
Microsoft Advertising
BootstrapCDN
Calendly
Facebook
GetSiteControl
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Optimize
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
Hotjar
Imgix
Iubenda
LinkedIn
Sectigo
Sentry
SlideShare
Spotify
YouTube
Zapier
Google Cloud
Certificate Information
Subject
CN=*.flexmail.eu
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36
Valid From
November 16, 2025
Valid Until
December 16, 2026
225 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
34:70:3A:54:73:8E:0F:51:9B:79:24:8D:14:93:0E:04:A3:49:C1:9D:06:CC:EB:AB:F1:3D:D9:DD:ED:F9:28:2A
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
Present
max-age=63072000
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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