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 portal-api.medianetpvt.com, portal.medianetpvt.com, not for stage-api.jicando.com

Cached · just now
92/100 SECURITY SCORE

Certificate Information

Subject
CN=portal-api.medianetpvt.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
December 08, 2025
Valid Until
March 08, 2026 40 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
A1:5E:51:2D:42:F6:8C:89:4D:EE:21:E6:52:B8:4D:A1:63:92:26:49:3D:60:9E:16:89:61:50:38:AC:13:5E:D2
Alternative Names
2 domains

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Good
default-src; base-uri; font-src; +8 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
  • • Consider adding 'preload' to HSTS for maximum security
  • • Strengthen CSP by removing 'unsafe-eval'
  • • 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

2 domains
portal-api.medianetpvt.com portal.medianetpvt.com