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 academy2.xtm.cloud, ask-tfx.xtm.cloud, ask-xtm.xtm.cloud, ask-xtrf.xtm.cloud, bi.xtm-intl.com, calc-instance.xtm-intl.com, careers.xtm.cloud, demo.xtm.ai, landing.xtm.ai, not for files.xtm.cloud

Cached · just now
86/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
Let's Encrypt logo Let's Encrypt

Certificate Information

Subject
CN=xtm.cloud
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 04, 2026
Valid Until
July 03, 2026 56 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
64:05:99:A8:58:31:EF:90:92:46:4C:6E:CC:7D:C2:C9:99:2C:27:47:89:DF:86:D0:E7:98:B5:F2:4C:72:49:03
Alternative Names
31 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
Excellent
max-age=31536000; includeSubDomains; preload;
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • 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
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Authorized CAs
amazontrust.com comodoca.com digicert.com letsencrypt.org pki.goog sectigo.com
Wildcard CAs
digicert.com letsencrypt.org pki.goog sectigo.com amazontrust.com comodoca.com
Incident Reporting
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • You have authorized 6 CAs - consider limiting to only the CAs you actively use