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

75/100 SECURITY SCORE

Certificate Information

Subject
O=Acme Co, CN=Kubernetes Ingress Controller Fake Certificate
Issuer
O=Acme Co, CN=Kubernetes Ingress Controller Fake Certificate
Valid From
January 26, 2026
Valid Until
January 26, 2027 364 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
88:C7:B0:86:CD:AA:F3:A2:9F:D6:BB:AD:B3:D1:09:BF:EB:44:8F:4C:BA:15:85:6F:32:13:EB:C7:D7:BF:BC:CA
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
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
  • Consider adding 'preload' to HSTS for maximum security
  • 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
CAA Issues
  • CRITICAL: Current certificate issuer 'O=Acme Co, CN=Kubernetes Ingress Controller Fake Certificate' is NOT authorized by CAA records. Authorized CAs: letsencrypt.org
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement
  • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
  • Consider adding 'issuewild' records to control wildcard certificate issuance

Subject Alternative Names

1 domain