Hostname
itv.uz
Last fetched
itv.uz resolves to 91.90.216.70, announced in 91.90.216.0/22 by NETKA-AS - NETKA TELEKOM LLC in UZ. itv.uz 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
- 91.90.216.70
91.90.216.0/22 · NETKA-AS - NETKA TELEKOM LLC · Tashkent, UZ
- 91.90.216.71
91.90.216.0/22 · NETKA-AS - NETKA TELEKOM LLC · Tashkent, UZ
- 91.90.216.90
91.90.216.0/22 · NETKA-AS - NETKA TELEKOM LLC · Tashkent, UZ
- 45.91.220.43
45.91.220.0/22 · ATURON - Turon Media XK · Tashkent, UZ
- 45.91.220.42
45.91.220.0/22 · ATURON - Turon Media XK · Tashkent, UZ
- 45.91.220.41
45.91.220.0/22 · ATURON - Turon Media XK · Tashkent, UZ
IPv6 resolution
No AAAA record for itv.uz is recorded in WhisperGraph.
Attribution
netka telekom
ORIGIN_AS
WHOIS identity
- Registrar
- registrar:'turon media' ??
Subdomains
| Subdomain |
|---|
| files.itv.uz |
| icyber.itv.uz |
| info.itv.uz |
| ns1.itv.uz |
| ns2.itv.uz |
| stat.itv.uz |
| stream2.itv.uz |
| stream3.itv.uz |
| web.itv.uz |
| www.itv.uz |
Showing 10 of 10 subdomains (10 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
- 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
- ns1.itv.uz
- ns2.itv.uz
- ns3.itv.uz
MX records
- emx.mail.ru
SPF policy
- include: _spf.mail.ru
- a: itv.uz
- mx: itv.uz
- ip: 94.232.24.3
Threat-feed evidence
History
Related pages
Pivot from itv.uz 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: "itv.uz"})-[: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.