Skip to content

Hostname

locanto.cl

Last fetched

locanto.cl resolves to 104.16.127.229, announced in 104.16.112.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. locanto.cl 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 · locanto.clRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/locanto.cl

Resolution chain

IPv6 resolution

No AAAA record for locanto.cl is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
registrar:marcaria.com international, inc.
Registrant organisation
yalwa

Subdomains

Subdomain
angol.locanto.cl
antofagasta.locanto.cl
araucania.locanto.cl
arica.locanto.cl
aricayparinacota.locanto.cl
atacama.locanto.cl
aysen.locanto.cl
biobio.locanto.cl
calama.locanto.cl
castro.locanto.cl
chillan.locanto.cl
colina.locanto.cl

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

  • cheryl.ns.cloudflare.com
  • phil.ns.cloudflare.com
  • 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

MX records

  • mars.intermailgate.com

SPF policy

  • ip: 91.203.100.0/22
  • a: locanto.cl
  • mx: locanto.cl
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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