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:

Hostname Mismatch - certificate is issued for sso-dev.test.duosecurity.com, *.sso-dev.test.duosecurity.com, not for ec2-44-253-39-255.us-west-2.compute.amazonaws.com

Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
CN=sso-dev.test.duosecurity.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
February 06, 2025
Valid Until
March 07, 2026 75 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
17:9E:56:5E:5F:C1:DF:B8:95:94:F9:E9:0E:FD:24:16:C6:FA:82:70:46:3B:5A:C8:66:03:1A:D3:AD:B4:D3:77
Alternative Names
2 domains

Security Configuration

TLS Protocols
TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=31536000
Content-Security-Policy
Strong
default-src; frame-src; script-src; +5 more
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • 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