Skip to content

Hostname

joigo.cl

Last fetched

joigo.cl resolves to 131.72.237.52, announced in 131.72.237.0/24 by AS263753 - SERVICIOS DE DATACENTER DATANETWORKS LIMITADA in CL. joigo.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 · joigo.clRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.2/10canon.whisper.security/host/joigo.cl

Resolution chain

IPv6 resolution

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

Attribution

servicios de datanetworks limitada

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:nic chile
Registrant organisation
sociedad comerical joigo ltda

Subdomains

Subdomain
cpanel.joigo.cl
cpcalendars.joigo.cl
cpcontacts.joigo.cl
mail.joigo.cl
ns1.joigo.cl
ns2.joigo.cl
srv01.joigo.cl
webdisk.joigo.cl
webmail.joigo.cl
whm.joigo.cl
www.joigo.cl

Showing 11 of 11 subdomains (11 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.nodo03.dnw.cl
  • ns1.joigo.cl
  • ns2.joigo.cl
  • 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

  • joigo.cl

SPF policy

  • a: joigo.cl
  • mx: joigo.cl
  • ip: 131.72.236.163
  • ip: 131.72.236.164
  • ip: 131.72.237.18
  • ip: 131.72.237.4
  • ip: 131.72.237.52
  • ip: 45.35.2.58
  • ip: 45.35.2.61

Threat-feed evidence

History

Related pages

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