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 portfolio.mftoday.com, not for ec2-3-7-24-121.ap-south-1.compute.amazonaws.com
Open
Cached
·
just now
90/100
SECURITY SCORE
Certificate Information
Subject
CN=portfolio.mftoday.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
August 12, 2025
Valid Until
September 10, 2026
286 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
0F:36:A5:80:64:75:9D:59:95:8C:76:F0:F0:D3:E5:95:4E:53:25:3D:AB:1C:DC:B8:0B:4A:92:9D:87:85:F4:84
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=31536000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Present
geolocation=(),sync-xhr=(),fullscreen=(self)
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
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