Skip to content

Hostname

telemetrybalkan.com

Last fetched

telemetrybalkan.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. telemetrybalkan.com 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 · telemetrybalkan.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/telemetrybalkan.com

Resolution chain

No IPv4 resolution is recorded for telemetrybalkan.com in WhisperGraph.

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of telemetrybalkan.com owner
Contact emails
0420a283-58b6-462f-8a28-6863bf535c97@identity-protect.org, 34b691dd-644b-4a9c-9ab4-02d861abe734@identity-protect.org, 355b8fb8-f733-430d-a6cb-cc67fd06c714@identity-protect.org, 990a6bf5-9150-4e24-ba70-be4796c0b9e0@identity-protect.org, bb0f7fd1-4361-45e9-a0b5-ca8a1498990f@identity-protect.org, e74531f9-e3d6-450d-85b6-0dc98de729d7@identity-protect.org

Subdomains

Subdomain
chat.telemetrybalkan.com
www.telemetrybalkan.com

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • ns-278.awsdns-34.com
  • ns-950.awsdns-54.net
  • 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
  • ns-1079.awsdns-06.org
  • ns-1752.awsdns-27.co.uk

MX records

  • mx.yandex.net

Threat-feed evidence

History

Related pages

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