Skip to content

Hostname

mymaze.com

Last fetched

mymaze.com resolves to 91.189.122.132, announced in 91.189.120.0/21 by NEXTHOP - Nexthop AS in NO. mymaze.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 · mymaze.comRouting diversity1.5/10Peering density5.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/mymaze.com

Resolution chain

IPv6 resolution

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

Attribution

nexthop

ORIGIN_AS

WHOIS identity

Registrar
iana:1001
Registrant organisation
maze feedback as
Contact emails
28xnmyrcoek5@privacy-protection.email, 2fkhimccxzru@spamprotection.email, 5urpmtwwmjxg@privacy-protection.email, 9sbgghebjswz@privacy-protection.email, aq7npqjfrdrx@spamprotection.email, bpncagn9oupn@privacy-protection.email, e4bhygvs5dbw@privacy-protection.email, ec7qqtgwfjar@privacy-protection.email, fyxrg9qpejbh@privacy-protection.email, gfeasacvx2gf@spamprotection.email, hewhbaw7pfxj@privacy-protection.email, jx3nkhjdk2sf@privacy-protection.email, ktpo6n7rvdhe@privacy-protection.email, mv8gmayeaiiu@privacy-protection.email, qmuof2xx7z7m@privacy-protection.email, rcxqc6tj4yjb@privacy-protection.email, tam5lgvcr7er@spamprotection.email, vkuzvu3ybyfd@privacy-protection.email, vw2nwspbh7we@privacy-protection.email, what5hiykwzs@spamprotection.email and 3 more

Subdomains

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

  • ns1.hyp.net
  • ns2.hyp.net
  • ns3.hyp.net

MX records

  • mymaze-com.mail.protection.outlook.com

SPF policy

  • redirect: mymaze.com.hosted.spf-report.com

Threat-feed evidence

History

Related pages

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