Hostname
5210y.com
Last fetched
5210y.com resolves to 103.216.228.58, announced in 103.216.228.0/24 by INTECLOU-CDNK-NET - INTECLOUD CDNK LTD in US. 5210y.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 103.216.228.58
103.216.228.0/24 · INTECLOU-CDNK-NET - INTECLOUD CDNK LTD · Los Angeles, US
- 103.216.228.59
103.216.228.0/24 · INTECLOU-CDNK-NET - INTECLOUD CDNK LTD · Los Angeles, US
- 156.240.110.244
156.240.110.0/24 · HKCICL-AS-AP - Hong Kong Communications International Co., Limited · Hong Kong, HK
- 156.240.110.248
156.240.110.0/24 · HKCICL-AS-AP - Hong Kong Communications International Co., Limited · Hong Kong, HK
- 16.162.235.165
16.162.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 18.166.174.197
18.166.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 202.181.1.43
202.181.0.0/22 · EDTCL-HK - EVERY DAY TECHNOLOGY CO. LIMITED · Mong Kok, HK
- 210.79.63.19
210.79.63.0/24 · EDTCL-HK - EVERY DAY TECHNOLOGY CO. LIMITED · Mong Kok, HK
- 43.198.198.107
43.198.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 54.46.75.85
54.46.0.0/17 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
IPv6 resolution
No AAAA record for 5210y.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
Mail and authentication
Nameservers
- edns152.ultradns.biz
- edns153.ultradns.biz
- edns152.ultradns.com
- edns153.ultradns.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
- edns152.ultradns.net
- edns153.ultradns.net
- edns152.ultradns.org
- edns153.ultradns.org
Threat-feed evidence
History
Related pages
Pivot from 5210y.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: "5210y.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.