Skip to content

Hostname

iyagames.com

Last fetched

iyagames.com resolves to 8.219.160.213, announced in 8.219.128.0/17 by ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. in SG. iyagames.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 · iyagames.comRouting diversity1.5/10Peering density7.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/iyagames.com

Resolution chain

IPv6 resolution

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

Attribution

hangzhou alibaba advertising

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of iyagames.com owner
Contact emails
rajesh.shukla33@gmail.com, 00372e7c-2daa-4a64-b7d8-c587de6620ad@identity-protect.org, 2df19c45-0828-45f1-850e-ea0e9a91d10e@identity-protect.org, 347effbe-8cec-461b-972a-285d73cc5eec@identity-protect.org, 8d61ef54-6056-40d4-a7f9-6c476238213f@identity-protect.org, 9298fb5f-0a45-477a-b85f-ed3830b6e4aa@identity-protect.org, b128aa02-8b81-446e-b607-7cc8ab470135@identity-protect.org, e1db9193-25f7-4379-98e3-0f5d417b3e23@identity-protect.org, owner-2130167@iyagames.com.whoisprivacyservice.org

Subdomains

Subdomain
osg.iyagames.com
www.iyagames.com

Showing 2 of 2 subdomains (2 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.

Sample inbound links

Mail and authentication

Nameservers

  • ns-122.awsdns-15.com
  • ns-593.awsdns-10.net
  • ns-1511.awsdns-60.org
  • ns-1671.awsdns-16.co.uk

MX records

  • mx1.feishu.cn
  • mx2.feishu.cn
  • mx3.feishu.cn

Threat-feed evidence

History

Related pages

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