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:
Invalid Certificate - the server's certificate is malformed or invalid
Open
Cached
·
just now
73/100
SECURITY SCORE
Certificate Information
Subject
C=DE, ST=Some-State, O=a4a GmbH
Issuer
C=DE, ST=Some-State, O=a4a GmbH
Valid From
June 07, 2021
Valid Until
June 05, 2031
1867 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
25:DA:61:40:9F:11:4C:DC:90:AF:B0:6C:1A:3D:FB:D1:B7:F4:C5:EB:33:75:75:57:3B:09:7F:1D:97:43:42:31
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
- • 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
Configured
(Restricts certificate issuance)
Current Issuer
Not Authorized
(Potential misconfiguration)
Authorized CAs
Incident Reporting
mailto:[email protected]
CAA Issues
- • CRITICAL: Current certificate issuer 'C=DE, ST=Some-State, O=a4a GmbH' is NOT authorized by CAA records. Authorized CAs: letsencrypt.org
Recommendations
- • Consider adding 'issuewild' records to control wildcard certificate issuance