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
57/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Someprovince, L=Sometown, O=none, OU=none, CN=localhost, UNKNOWN=webmaster@localhost
Issuer
C=US, ST=Someprovince, L=Sometown, O=none, OU=none, CN=localhost, UNKNOWN=webmaster@localhost
Valid From
July 08, 2017
Valid Until
November 22, 2044 6593 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA1-RSA Weak
SHA-256 Fingerprint
D0:E5:5F:71:6B:8B:0F:CA:3E:DC:6D:11:82:B6:3F:2D:FC:02:9A:52:58:0B:92:69:B9:14:A3:40:73:0D:AD:E7

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)
  • • TLS 1.1 is deprecated and should be disabled
  • • TLS 1.0 is deprecated and should be disabled

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
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
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