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 www.chfa.org, not for chfa.org

Cached · just now
73/100 SECURITY SCORE

Certificate Information

Subject
UNKNOWN={:asn1_OPENTYPE, <<19, 2, 85, 83>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 11, 67, 111, 110, 110, 101, 99, 116, 105, 99, 117, 116>>}, UNKNOWN={:asn1_OPENTYPE, <<12, 17, 71, 111, 118, 101, 114, 110, 109, 101, 110, 116, 32, 69, 110, 116, 105, 116, 121>>}, UNKNOWN=Government Entity, C=US, ST=Connecticut, L=Rocky Hill, O=Connecticut Housing Finance Authority, CN=www.chfa.org
Issuer
C=US, O=DigiCert Inc, CN=DigiCert EV RSA CA G2
Valid From
January 05, 2026
Valid Until
February 05, 2027 366 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8A:9B:3B:D9:A1:AF:E3:7A:1F:F3:76:F2:39:E1:63:93:32:F4:4C:B2:25:53:A3:0B:B5:D6:BD:18:1B:9F:7C:A1
Alternative Names

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

Subject Alternative Names

1 domain