Skip to content

Hostname

tg.get.run

Last fetched

tg.get.run resolves to 2 IPv4 addresses operated by AS210079 in RU.

Nutrition Label

WHISPER CANON · tg.get.runRouting diversity2.4/10Peering density6.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/tg.get.run

Resolution chain

tg.get.run resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

WHOIS identity

No WHOIS records are currently associated with tg.get.run in WhisperGraph.

Subdomains

1 observed subdomain of tg.get.run.

Threat posture

History

Mail and authentication

MX records

  • tg.get.run

SPF policy

4 SPF mechanisms authorising senders for tg.get.run.

MechanismTarget
SPF_Amail.menodom.deserv.net
SPF_Atg.get.run
SPF_IP185.12.92.131
SPF_MXtg.get.run

Related pages

Pivot deeper into the graph from tg.get.run.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "tg.get.run"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.