Skip to content

Hostname

mazooma.com

Last fetched

mazooma.com resolves to 15.223.63.112, announced in 15.222.0.0/15 by AMAZON-02 - Amazon.com, Inc. in CA. mazooma.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 · mazooma.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/mazooma.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
on behalf of mazooma.com owner
Contact emails
082bcc9c0a28fd0a79ae7f53b8569299@domaindiscreet.com, 0hplh1vvhchq2bn9j0nf645cfa@domaindiscreet.com, 570de5870a28fd0a7344424a4231ec23@domaindiscreet.com, 1519ac4a-e1d1-4f1f-b8db-f81bfd1a4005@identity-protect.org, 2b9730c5-8b70-41d1-b3e7-85c1393ed9f1@identity-protect.org, 39c50186-fcc3-4297-8800-d233d8e1e2d5@identity-protect.org, c201d39d-e74d-4ea8-84ca-aa79a87e5ebd@identity-protect.org, owner-5366400@mazooma.com.whoisprivacyservice.org, owner-8845789@mazooma.com.whoisprivacyservice.org, owner-9313120@mazooma.com.whoisprivacyservice.org

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

  • ns-217.awsdns-27.com
  • ns-693.awsdns-22.net
  • ns-1064.awsdns-05.org
  • ns-1929.awsdns-49.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: _spf.goskope.com
  • include: mailcontrol.com

Threat-feed evidence

History

Related pages

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