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 secure.danaconnect.com, not for danaconnect.com
Open
Cached
·
just now
94/100
SECURITY SCORE
Certificate Information
Subject
CN=secure.danaconnect.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
May 13, 2025
Valid Until
June 11, 2026
161 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
7B:45:5B:E2:06:A4:55:EC:C4:BB:98:2A:36:85:23:0A:C9:AF:5B:85:50:16:D9:C0:84:59:92:39:BD:D2:0E:D3
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Excellent
deny
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=(self "https://secure.danaconnect.com" "https://portal.danaconnect.com"), encrypted-media=(), payment=(), usb=()
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 8 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance