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 eshop.bystadium.com, *.bystadium.com, not for ec2-34-195-55-38.compute-1.amazonaws.com
Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=eshop.bystadium.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
February 17, 2025
Valid Until
March 19, 2026
112 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
DA:C0:B9:BB:AF:A2:4A:8B:1C:13:E0:A0:15:99:E4:8A:6A:DF:4B:D7:08:70:3D:14:5A:23:19:6F:6B:0C:75:92
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
Content-Security-Policy
Weak
frame-ancestors; form-action
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
ch-dpr=("https://res.cloudinary.com"), ch-width=("https://res.cloudinary.com"), ch-viewport-width=("https://res.cloudinary.com")
Recommendations
- • Significantly strengthen CSP directives
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