Hostname
tele-m.com
Last fetched
tele-m.com resolves to 176.57.64.233, announced in 176.57.64.0/23 by DDOS-GUARD - DDOS-GUARD LTD in RU. tele-m.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 176.57.64.233
176.57.64.0/23 · DDOS-GUARD - DDOS-GUARD LTD · Moscow, RU
- 5.35.96.165
5.35.96.0/23 · RU-JSCIOT - JSC IOT · Moscow, RU
IPv6 resolution
No AAAA record for tele-m.com is recorded in WhisperGraph.
Attribution
ddos guard
DNS_OPERATOR, ORIGIN_AS
WHOIS identity
- Registrar
- iana:1606
- Registrant organisation
- personal data, can not be publicly disclosed according to applicable laws.
- Contact emails
- anna@dimeco.ru, tele-m.com@regprivate.ru
Subdomains
Showing 3 of 3 subdomains (3 per page).
Mail and authentication
Nameservers
- tele-m.com
- fns.medbank.pro
- sns.medbank.pro
MX records
- mail.tele-m.com
SPF policy
- a: tele-m.com
- mx: tele-m.com
- a: _spf.medbank.pro
- a: _spf2.medbank.pro
Threat-feed evidence
History
Related pages
Pivot from tele-m.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: "tele-m.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.