Hostname
tya.zone
Last fetched
tya.zone resolves to 14 IPv4 addresses operated by AGERA TELECOMUNICACOES SA in CN. WHOIS lists iana:1599 as the registrar.
Nutrition Label
Resolution chain
tya.zone resolves to 14 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 106.225.194.35 | 106.225.192.0/18 | AS134238 | AGERA TELECOMUNICACOES SA | CN |
| 111.225.213.35 | 111.225.213.0/24 | AS58539 | SIS-AS-AP Sundaram Infotech SolutionsA Division of Sundaram Finance | CN |
| 113.142.207.35 | 113.142.128.0/17 | AS134768 | BNIPL-AS Broad Net India Private Limited | CN |
| 117.68.56.35 | 117.68.56.0/22 | AS134425 | NEWWEB | CN |
| 119.167.237.35 | 119.164.0.0/14 | AS4837 | CHINA169-BACKBONE CHINA UNICOM China169 Backbone | CN |
| 123.235.30.35 | 123.232.0.0/14 | AS4837 | CHINA169-BACKBONE CHINA UNICOM China169 Backbone | CN |
| 124.226.72.35 | 124.226.72.0/22 | AS137693 | CHARTER-BGP-INFRASTRUCTURE - Charter Communications LLC | CN |
| 150.138.253.35 | 150.138.224.0/19 | AS58540 | CHINATELECOM-HEBEI-LANGFANG-IDC Langfang,Hebei province, P.R.China | CN |
| 171.107.86.35 | 171.107.84.0/22 | AS138169 | NET-CONNECT-AS | CN |
| 171.109.97.35 | 171.109.96.0/20 | AS138169 | NET-CONNECT-AS | CN |
| 175.12.90.35 | 175.12.64.0/18 | AS151823 | IMPERIAL INTERNET E TELECOMUNICACOES LTDA | CN |
| 180.97.198.35 | 180.97.198.0/23 | AS140292 | CONECTARED SA DE CV | CN |
| 183.60.227.35 | 183.60.224.0/21 | AS134763 | PITC-VN PITC Investment Joint Stock Company | CN |
| 42.101.56.35 | 42.101.56.0/22 | AS137698 | AAACT-AS-IN Aaacloud Telephony Pvt Ltd | CN |
WHOIS identity
- Registrar
- iana:1599
- Organization
- tian yong an
- Contact emails
- —
Subdomains
1 observed subdomain of tya.zone.
| Subdomain |
|---|
| www.tya.zone |
Web-graph footprint
Distinct hostnames that link to or from tya.zone in the public web crawl.
Threat posture
History
Related pages
Pivot deeper into the graph from tya.zone.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "tya.zone"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.