Skip to content

Hostname

stadium.com.uy

Last fetched

stadium.com.uy resolves to 45.33.97.37, announced in 45.33.96.0/21 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. stadium.com.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 · stadium.com.uyRouting diversity1.5/10Peering density5.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/stadium.com.uy

Resolution chain

IPv6 resolution

No AAAA record for stadium.com.uy is recorded in WhisperGraph.

Attribution

akamai

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for stadium.com.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
atencionalcliente.stadium.com.uy
correo.stadium.com.uy
www.stadium.com.uy

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

  • ns1.netuy.net
  • ns2.netuy.net
  • ns3.netuy.net
  • s1127.nty.uy

MX records

  • correo.cybe.com.uy

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: spf.mandrillapp.com
  • include: musvc.com
  • include: mail.zendesk.com
  • include: servers.mcsv.net
  • a: stadium.com.uy
  • mx: stadium.com.uy
  • mx: correo.stadium.com.uy
  • ip: 179.27.76.130
  • ip: 179.27.76.132
  • ip: 200.58.149.123

Threat-feed evidence

History

Related pages

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