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 autoconfig.atnhg.com, autoconfig.calinet.us, autoconfig.gen-techsupport.com, autoconfig.prkhg.com, autoconfig.rivere.dev, autoconfig.super8wbr.com, autodiscover.atnhg.com, autodiscover.calinet.us, autodiscover.gen-techsupport.com, not for dev.dhtmlx.com

Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
CN=mailcow.mailsynergy.net
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 01, 2026
Valid Until
June 30, 2026 48 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E5:F9:7C:EB:E0:0C:45:0C:BA:AB:45:4A:C2:1B:53:A8:B6:39:B7:6B:0D:D3:58:F2:8E:B4:11:7D:8A:EA:B1:BE
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=15768000;
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-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