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 a2.netiserver.com, cpanel.a2.netiserver.com, cpcalendars.a2.netiserver.com, cpcontacts.a2.netiserver.com, mail.a2.netiserver.com, webmail.a2.netiserver.com, whm.a2.netiserver.com, www.a2.netiserver.com, not for webmail.netiserver.eu
Open
Cached
·
just now
81/100
SECURITY SCORE
Certificate Information
Subject
CN=a2.netiserver.com
Issuer
C=US, O=cPanel, LLC, CN=cPanel ECC Domain Validation Secure Server CA 3
Valid From
April 01, 2026
Valid Until
June 30, 2026
44 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
1C:B8:3C:F8:83:AC:57:72:EC:2D:60:7F:24:3A:8B:BE:E5:FF:0E:89:94:C2:4D:9C:18:70:A1:19:10:D6:C3:75
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
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