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 *.content.snapcomms.com, *.snapcomms.com, *.svc.snapcomms.com, snapcomms.com, not for teal.use.snapcomms.com

89/100 SECURITY SCORE

Certificate Information

Subject
CN=*.svc.snapcomms.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
January 26, 2026
Valid Until
April 26, 2026 89 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
36:6B:FC:DF:F1:2A:2C:5F:B3:37:7D:81:8D:0A:94:2B:21:8F:93:F9:E4:D6:DA:E0:4B:C4:84:ED:A6:94:3C:9A
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
Excellent
max-age=31536000; includeSubDomains; preload;
Content-Security-Policy
Basic
default-src; script-src; connect-src; +5 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • 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