Skip to content

Hostname

controlkilos.org

Last fetched

controlkilos.org resolves to 65.109.31.34, announced in 65.109.0.0/16 by HETZNER-AS - Hetzner Online GmbH in FI. controlkilos.org 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 · controlkilos.orgRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/controlkilos.org

Resolution chain

IPv6 resolution

No AAAA record for controlkilos.org is recorded in WhisperGraph.

Attribution

hetzner

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
carolina cesar
Contact emails
masterplan@adinet.com.uy

Subdomains

Subdomain
agenda.controlkilos.org
aplicacion.controlkilos.org
costarica.controlkilos.org
cpanel.controlkilos.org
cpcalendars.controlkilos.org
cpcontacts.controlkilos.org
ecuador.controlkilos.org
mail.controlkilos.org
mi.controlkilos.org
miplanilla.controlkilos.org
paraguay.controlkilos.org
participantes.controlkilos.org

Showing 12 of 27. View all subdomains →

Mail and authentication

Nameservers

  • ns1.65-109-31-34.cprapid.com
  • ns2.65-109-31-34.cprapid.com
  • ns1.cprapid.com
  • ns2.cprapid.com
  • ns352.hostingmontevideo.com
  • ns353.hostingmontevideo.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

  • controlkilos.org

SPF policy

  • a: controlkilos.org
  • mx: controlkilos.org
  • ip: 138.201.207.68
  • ip: 148.72.153.75
  • ip: 65.109.31.34

Threat-feed evidence

History

Related pages

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