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 *.env1.dev.ingenio.com, *.env3.dev.ingenio.com, *.env5.dev.ingenio.com, *.env10.dev.ingenio.com, *.env7.dev.ingenio.com, *.env4.dev.ingenio.com, *.env2.dev.ingenio.com, *.env8.dev.ingenio.com, *.env9.dev.ingenio.com, not for dev.sonosim.com

Cached · just now
70/100 SECURITY SCORE

Certificate Information

Subject
CN=*.env1.dev.ingenio.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
May 29, 2025
Valid Until
June 27, 2026 139 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
50:1E:92:10:57:DE:13:9A:56:A1:6E:D6:77:1A:37:01:66:55:82:4A:7C:10:38:95:2E:7A:88:90:38:D6:71:DA
Alternative Names

Security Configuration

TLS Protocols
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

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
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