Skip to content

Hostname

cabal.com.uy

Last fetched

cabal.com.uy resolves to 104.26.14.101, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. cabal.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 · cabal.com.uyRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/cabal.com.uy

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for cabal.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
acceso-cdlc.cabal.com.uy
acceso.cabal.com.uy
apps.cabal.com.uy
ba.cabal.com.uy
comunidad.cabal.com.uy
google-agent.cabal.com.uy
google-migrate.cabal.com.uy
mantis.cabal.com.uy
mobile-app-staging.cabal.com.uy
mobile-app.cabal.com.uy
penca.cabal.com.uy
pitagoras.cabal.com.uy

Showing 12 of 22. 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

Mail and authentication

Nameservers

  • noor.ns.cloudflare.com
  • osmar.ns.cloudflare.com

MX records

  • smtp.google.com
  • cabaluruguay.in.tmes.trendmicro.com

SPF policy

  • include: _spf.google.com
  • include: spf.tmes.trendmicro.com
  • include: sendgrid.net
  • mx: cabal.com.uy

Threat-feed evidence

History

Related pages

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