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 *.appranix.net, appranix.net, not for lexi.bycopilot.com
Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=New Jersey, L=Tinton Falls, O=Commvault Systems, Inc., CN=*.appranix.net
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
January 21, 2025
Valid Until
January 20, 2026
43 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
9F:77:54:0E:74:6F:1A:DF:1B:CE:45:3F:A3:5A:B7:0F:C2:02:78:11:77:BD:E7:41:BD:2D:5C:AA:ED:6F:DC:6B
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
Weak
Strict-Transport-Security
Content-Security-Policy
Good
default-src; img-src; connect-src; +4 more
default-src 'self' https://*.appranix.net; img-src 'self' https://*.appranix.net https://www.googletagmanager.com https://www.gstatic.com https://www.google.co.in data:; connect-src 'self' https://*.appranix.net https://*.google-analytics.com https://analytics.google.com https://*.g.doubleclick.net; script-src 'self' https://*.appranix.net https://www.gstatic.com https://www.googletagmanager.com https://www.google.com https://www.google.co.in 'unsafe-inline'; style-src 'self' https://*.appranix.net https://use.fontawesome.com https://fonts.googleapis.com 'unsafe-inline'; font-src 'self' https://fonts.googleapis.com https://fonts.gstatic.com https://use.fontawesome.com https://*.appranix.net; frame-src https://td.doubleclick.net https://www.google.com;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • 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