Skip to content

Hostname

lootx.com

Last fetched

lootx.com resolves to 104.26.12.57, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. lootx.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 · lootx.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/lootx.com

Resolution chain

IPv6 resolution

IPv6 resolution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Attribution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

WHOIS identity

Registrar
iana:1479
Registrant organisation
bryce pasechnik
Contact emails
bryce@vericlock.com, pw-838abf4e1776e9a92040cccb60def7d6@privacyguardian.org, pw-86dca99bf79201c948a50a1375c0d491@privacyguardian.org, pw-9801309fbb7cd8525626c1e467cfeb08@privacyguardian.org

Subdomains

Subdomains is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Mail and authentication

Nameservers

  • cloe.ns.cloudflare.com
  • jake.ns.cloudflare.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

  • arrow.mxrouting.net
  • arrow-relay.mxrouting.net

SPF policy

  • include: spf.mailjet.com
  • include: mxlogin.com

Threat-feed evidence

History

Related pages

Pivot from lootx.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: "lootx.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.