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 mail.nodovip.com, mail.recaptymulticobro.com, mail.sicobec.com, tc77.reverseptr.net, not for dns3.nodovip.com
Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=mail.nodovip.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
November 21, 2025
Valid Until
February 19, 2026
76 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
71:C7:B8:B1:05:C8:19:50:6D:FB:FB:86:E0:3C:FA:5D:EE:81:1D:CA:1D:80:51:A1:B5:3A:39:DE:BB:C4:25:D0
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=31536000
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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
Subject Alternative Names
4 domains
mail.nodovip.com
mail.recaptymulticobro.com
tc77.reverseptr.net
mail.sicobec.com
Other domains in certificate