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 venture.com, www.mark.com, www.venture.com, preprod.mark.com, preprod.venture.com, mark.com, not for noogle.com
Open
Cached
·
just now
87/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=venture.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
February 10, 2026
Valid Until
March 11, 2027
126 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E2:F5:4B:45:7B:AF:3C:DC:FF:50:2B:72:B4:EB:76:40:0D:E2:22:A9:F6:E4:FA:3E:23:77:2F:0F:4D:21:67:B7
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
Present
max-age=63072000
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Not Authorized
(Potential misconfiguration)
CAA Issues
- • CRITICAL: Current certificate issuer 'C=US, O=Amazon, CN=Amazon RSA 2048 M04' is NOT authorized by CAA records. Authorized CAs:
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts