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 alphastar.intellimedianetworks.net, beta.intellimedianetworks.com, heartcore.intellimedianetworks.net, hrms.intellimedianetworks.com, live.mixie.app, mixiehub.com, platform.mixie.app, ravalwest.com, sisley.intellimedianetworks.net, not for ec2-54-161-50-155.compute-1.amazonaws.com

75/100 SECURITY SCORE

Certificate Information

Subject
CN=alphastar.intellimedianetworks.net
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
December 05, 2025
Valid Until
March 05, 2026 89 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B0:95:3A:E7:9E:88:0A:EA:82:00:D4:50:2E:E1:FC:12:22:E6:19:9C:74:DB:48:99:44:AA:A1:03:AF:8A:71:0C
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
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
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 X-Content-Type-Options: nosniff
  • 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