Hostname
api.tmtreader.com
Last fetched
api.tmtreader.com resolves to 2.22.50.206, announced in 2.22.50.0/24 by AKAMAI-ASN1 - Akamai International B.V. in DE. api.tmtreader.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
- 2.22.50.206
2.22.50.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 2.23.6.58
2.23.6.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 2.23.6.7
2.23.6.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 23.212.191.36
23.212.191.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Brasília, BR
- 23.212.191.45
23.212.191.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Brasília, BR
- 23.51.25.11
23.51.25.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Elk Grove Village, US
- 23.51.25.13
23.51.25.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Elk Grove Village, US
- 2.22.50.213
2.22.50.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for api.tmtreader.com is recorded in WhisperGraph.
Attribution
akamai international
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for api.tmtreader.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- n0api4.akamaiedge.net
- n1api4.akamaiedge.net
- n2api4.akamaiedge.net
- n3api4.akamaiedge.net
- n4api4.akamaiedge.net
- n5api4.akamaiedge.net
- n6api4.akamaiedge.net
- n7api4.akamaiedge.net
Threat-feed evidence
History
Related pages
Pivot from api.tmtreader.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: "api.tmtreader.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.