Skip to content

Hostname

jtlxpress.com

Last fetched

jtlxpress.com resolves to 104.21.71.235, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. jtlxpress.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · jtlxpress.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.6/10canon.whisper.security/host/jtlxpress.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · MAIL_RECEIVER, ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1387
Contact emails
info@domain-contact.org

Subdomains

Subdomain
app.jtlxpress.com
autodiscover.jtlxpress.com
business.jtlxpress.com
com.jtlxpress.com
cpanel.jtlxpress.com
cpcalendars.jtlxpress.com
cpcontacts.jtlxpress.com
mail.jtlxpress.com
webdisk.jtlxpress.com
webmail.jtlxpress.com
www.jtlxpress.com

Showing 11 of 15. View all subdomains →

Mail and authentication

Nameservers

  • chloe.ns.cloudflare.com
  • phil.ns.cloudflare.com
  • ns1.mysecurecloudhost.com
  • ns2.mysecurecloudhost.com
  • ns3.mysecurecloudhost.com
  • ns4.mysecurecloudhost.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • jtlxpress.com
  • mx.zoho.com
  • mx2.zoho.com
  • mx3.zoho.com
  • _dc-mx.90cd8d920c97.jtlxpress.com

SPF policy

  • a: jtlxpress.com
  • mx: jtlxpress.com
  • include: spf.mysecurecloudhost.com
  • ip: 147.135.15.137
  • ip: 147.135.4.168
  • ip: 147.135.91.12
  • ip: 192.243.110.5
  • ip: 51.178.74.177

Threat-feed evidence

History

Related pages

Pivot from jtlxpress.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "jtlxpress.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.