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.adm.tools, mail.ukraine.com.ua, web431.default-host.net, not for mail.psy-school.com

89/100 SECURITY SCORE

Certificate Information

Subject
CN=mail.adm.tools
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 18, 2026
Valid Until
July 17, 2026 65 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
00:DF:F3:7A:67:AF:40:31:2A:6C:03:4A:2B:0E:A7:AF:0C:85:04:3D:3A:AC:9D:E9:59:CA:BA:51:78:89:A3:30
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
Good
default-src; form-action; child-src; +10 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
Deny
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
accelerometer=(self), autoplay=(self), camera=(self); +21 more
Recommendations
  • Strengthen CSP by removing 'unsafe-eval'
  • Add X-Content-Type-Options: nosniff
  • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)

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