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 *.pro-ext.dracoon.net, pro-ext.dracoon.net, not for dracoon.cloud
Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=*.pro-ext.dracoon.net
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
February 16, 2026
Valid Until
May 17, 2026
35 days
Public Key
ECDSA
384 bit
(P-384)
Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
21:76:B0:9D:3A:A0:A4:4A:89:5D:C8:1F:FA:B9:AF:41:BC:7D:3E:E3:BC:CE:45:1F:92:79:15:0A:9A:F9:20:ED
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
Excellent
max-age=63072000; includeSubDomains; preload
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Significantly strengthen CSP directives
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Incident Reporting
mailto:[email protected]
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'issuewild' records to control wildcard certificate issuance