Skip to content

Hostname

tigoweb.com

Last fetched

tigoweb.com resolves to 116.118.49.140, announced in 116.118.48.0/22 by AZDIGI-AS-VN - AZDIGI Corporation in VN. tigoweb.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Mon, 14 Sep 2026 09:18:44 GMT
Last seen on a feed
Fri, 25 Sep 2026 00:02:39 GMT

Nutrition Label

WHISPER CANON · tigoweb.comRouting diversity2.4/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/tigoweb.com

Resolution chain

IPv6 resolution

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

Attribution

azdigi

ORIGIN_AS

WHOIS identity

Registrar
iana:3234
Registrant organisation
domain admin, c/o id#10760
Contact emails
ryjkklvb@whoisprivacyprotect.com, xgdyqgtjch@whoisprivacyprotect.com, privacyprotect@inet.vn

Subdomains

Subdomain
bienhoa.tigoweb.com
theme.tigoweb.com
www.tigoweb.com

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

Sample outbound 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
  • ns-master.inet.vn
  • ns1.inet.vn
  • ns2.inet.vn
  • ns3.inet.vn

Threat-feed evidence

History

Related pages

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