DNS Gurus

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

Cached · just now
75/100 SECURITY SCORE

Certificate Information

Subject
CN=TRAEFIK DEFAULT CERT
Issuer
CN=TRAEFIK DEFAULT CERT
Valid From
January 06, 2026
Valid Until
January 06, 2027 364 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
28:A2:9E:AB:D0:9F:6A:7D:9F:EE:28:A5:CA:98:1E:95:37:15:C1:F7:A8:29:7A:A6:88:47:07:BA:EE:20:D4:C7
Alternative Names
1 domains

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
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
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 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
comodoca.com letsencrypt.org pki.goog digicert.com sectigo.com globalsign.com
Wildcard CAs
pki.goog globalsign.com digicert.com letsencrypt.org sectigo.com comodoca.com
CAA Issues
  • • CRITICAL: Current certificate issuer 'CN=TRAEFIK DEFAULT CERT' is NOT authorized by CAA records. Authorized CAs: comodoca.com, letsencrypt.org, pki.goog, digicert.com, sectigo.com, globalsign.com
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • You have authorized 6 CAs - consider limiting to only the CAs you actively use
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts