DNS Gurus

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.stygius.scriptcase.host, autodiscover.stygius.scriptcase.host, cpanel.stygius.scriptcase.host, cpcalendars.stygius.scriptcase.host, cpcontacts.stygius.scriptcase.host, ipv6.stygius.scriptcase.host, mail.stygius.scriptcase.host, stygius.scriptcase.host, webdisk.stygius.scriptcase.host, not for ns2-stygius.scriptcase.host

Cached · just now
71/100 SECURITY SCORE

Certificate Information

Subject
CN=stygius.scriptcase.host
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
December 11, 2025
Valid Until
March 11, 2026 44 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D0:2E:EE:C2:48:69:DE:0B:2E:F5:B2:35:3F:B0:70:0A:7F:E9:14:BB:AE:22:A1:54:0A:AF:2B:EC:66:22:28:E3
Alternative Names
12 domains

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
Missing
Not configured
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 X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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