Skip to content

Hostname

lunchboxrecords.com

Last fetched

lunchboxrecords.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. lunchboxrecords.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 · lunchboxrecords.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/lunchboxrecords.com

Resolution chain

No IPv4 resolution is recorded for lunchboxrecords.com in WhisperGraph.

IPv6 resolution

No AAAA record for lunchboxrecords.com is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:9
Registrant organisation
domain protection services,
Contact emails
03077af50a28fd0a001928998e54448a@domaindiscreet.com, 72874fcc0a28fd0a517114e95c5b3884@domaindiscreet.com, 87bb47290a28fd0a2d6760fa5c8600da@domaindiscreet.com, c90b9a760a28fd0a0ded1e69afd0bfa2@domaindiscreet.com, ch4m3h2oeahuia3966s1blfkq6@domaindiscreet.com

Subdomains

Showing 1 of 1 subdomain (1 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns1glr.name.com
  • ns2nsw.name.com
  • ns3fgh.name.com
  • ns4htz.name.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

Threat-feed evidence

History

Related pages

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