Hostname
telogrem.com
Last fetched
telogrem.com resolves to 104.21.50.61, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. telogrem.com is listed by 2 threat feeds; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 2 threat feeds. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:49:47 GMT
- Last seen on a feed
- Mon, 21 Sep 2026 23:09:40 GMT
Nutrition Label
Resolution chain
- 104.21.50.61
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.157.138
172.67.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 47.76.127.217
47.76.0.0/17 · ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. · Hong Kong, HK
- 47.91.170.222
47.91.128.0/18 · ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. · Hong Kong, HK
- 8.218.208.240
8.218.128.0/17 · ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. · Hong Kong, HK
- 85.239.243.252
85.239.240.0/21 · CONTABO-40021 - Contabo Inc. · St Louis, US
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1923
- Registrant organisation
- privacy service provided by withheld for privacy ehf
- Contact emails
- 035e769ff03d4410a9f9e0d7f84fe525.protect@withheldforprivacy.com
Subdomains
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns1.alidns.com
- ns2.alidns.com
- ns7.alidns.com
- ns8.alidns.com
- emely.ns.cloudflare.com
- theo.ns.cloudflare.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
- ns1.nameoffice.com
- ns2.nameoffice.com
Threat-feed evidence
History
Related pages
Pivot from telogrem.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: "telogrem.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.