Skip to content

Hostname

zenmatchgame.com

Last fetched

zenmatchgame.com resolves to 13.225.134.116, announced in 13.225.134.0/24 by AMAZON-02 - Amazon.com, Inc. in KR. zenmatchgame.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 · zenmatchgame.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/zenmatchgame.com

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of zenmatchgame.com owner
Contact emails
12576803-8fe0-44c2-be3b-9c4039828783@identity-protect.org, 14383a40-b5ca-483c-85cb-0ebff33c69fa@identity-protect.org, 228381a9-0a85-42da-89ae-5857d635e6a5@identity-protect.org, 6c8e724a-2240-423d-9734-814839d71e43@identity-protect.org, 7b6c2688-a05d-4f6a-ba0f-aa7da496f9d9@identity-protect.org, e4728984-9de5-4333-a2a2-e0afb9a14026@identity-protect.org, fa8d53bf-9faf-4c71-9308-85b67b5d5b37@identity-protect.org, owner-10018232@zenmatchgame.com.whoisprivacyservice.org, owner-8963952@zenmatchgame.com.whoisprivacyservice.org

Subdomains

Subdomain
a-grpc.zenmatchgame.com
a.zenmatchgame.com
api.zenmatchgame.com
b-grpc.zenmatchgame.com
b.zenmatchgame.com
beta-grpc.zenmatchgame.com
beta.zenmatchgame.com
fingu.zenmatchgame.com
glb-gjg.zenmatchgame.com
logger.zenmatchgame.com

Showing 10 of 24. View all subdomains →

Mail and authentication

Nameservers

  • hadlee.ns.cloudflare.com
  • mike.ns.cloudflare.com

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

SPF policy

  • include: _spf.google.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

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