Skip to content

Hostname

totalnet.uy

Last fetched

totalnet.uy resolves to 20.237.117.190, announced in 20.192.0.0/10 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. totalnet.uy 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 · totalnet.uyRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/totalnet.uy

Resolution chain

IPv6 resolution

No AAAA record for totalnet.uy is recorded in WhisperGraph.

Attribution

Github

saas · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for totalnet.uy. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
appgw-eus-1.totalnet.uy
appgw.totalnet.uy
conecta.totalnet.uy
email.totalnet.uy
files.totalnet.uy
info.totalnet.uy
news.totalnet.uy
pagos.totalnet.uy
sbc01.totalnet.uy
testfrontdoor.totalnet.uy

Showing 10 of 14. View all subdomains →

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

  • ns1-02.azure-dns.com
  • ns4-02.azure-dns.info
  • ns2-02.azure-dns.net
  • ns3-02.azure-dns.org

MX records

  • totalnet-uy.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: spf.sendinblue.com
  • include: mailgun.org
  • mx: totalnet.uy
  • ip: 190.64.146.156
  • ip: 20.228.166.61
  • ip: 200.58.150.212
  • ip: 200.58.150.218
  • ip: 200.58.150.219
  • ip: 201.217.155.106

Threat-feed evidence

History

Related pages

Pivot from totalnet.uy 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: "totalnet.uy"})-[: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.