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:
Invalid Certificate - the server's certificate is malformed or invalid
Open
Cached
·
just now
43/100
SECURITY SCORE
Certificate Information
Subject
CN=webphp53-1.mutu.nnx.com
Issuer
CN=webphp53-1.mutu.nnx.com
Valid From
February 25, 2014
Valid Until
February 23, 2024
Expired
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA1-RSA
Weak
SHA-256 Fingerprint
01:3F:63:C6:60:F7:B6:6E:19:12:B3:AD:F8:E1:0F:19:86:88:C1:09:1A:3F:26:43:FD:FF:8F:E4:F7:3D:6B:B8
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
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