SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Hostname Mismatch - certificate is issued for *.myacolad.eu, myacolad.eu, not for ec2-35-157-239-55.eu-central-1.compute.amazonaws.com
Open
Cached
·
just now
79/100
SECURITY SCORE
Certificate Information
Subject
CN=*.myacolad.eu
Issuer
C=GB, ST=Greater Manchester, L=Salford, O=Sectigo Limited, CN=Sectigo RSA Domain Validation Secure Server CA
Valid From
December 16, 2024
Valid Until
December 26, 2025
17 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
3E:AE:5B:10:6C:AD:92:B3:5D:36:3D:2A:30:69:34:F4:7F:AD:C1:59:D7:C3:71:EC:50:D4:3C:EC:2A:08:98:D1
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Excellent
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Basic
default-src; script-src; style-src; +7 more
default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://ajax.googleapis.com https://js.hcaptcha.com https://*.appcues.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://fonts.google.com https://*.appcues.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https://res.cloudinary.com https://cdn.jsdelivr.net https://*.appcues.com; connect-src 'self' https://*.appcues.com wss://*.appcues.net wss://*.appcues.net https://*.myacolad.eu wss://*.myacolad.eu https://*.acolad.com wss://*.acolad.com https://*.hcaptcha.com https://*.amazonaws.com; frame-src 'self' https://*.appcues.com https://*.hcaptcha.com; frame-ancestors 'self' https://s1.ariba.com https://s1-eu.ariba.com; object-src 'none'; base-uri 'self';
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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