Hostname
ker3000.com
Last fetched
ker3000.com resolves to 104.21.68.70, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ker3000.com is listed by 3 threat feeds; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 3 threat feeds. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 3
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:51:23 GMT
- Last seen on a feed
- Mon, 07 Sep 2026 00:02:26 GMT
Nutrition Label
Resolution chain
- 104.21.68.70
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 154.89.83.15
154.89.64.0/18 · HKIDC-AS-AP - LUOGELANG (FRANCE) LIMITED · Hong Kong, HK
- 172.67.191.168
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.65.211.209
172.65.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 43.165.0.18
43.165.0.0/18 · TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue · Frankfurt am Main, DE
- 36.53.0.50
36.53.0.0/17 · SAKURA-B - SAKURA Internet Inc. · Osaka, JP
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1923
- Registrant organisation
- domain administrator
- Contact emails
- backorder@dotmedia.com, dbsvn214@gmail.com
Subdomains
Showing 3 of 3 subdomains (3 per page).
Mail and authentication
Nameservers
- anita.ns.cloudflare.com
- brad.ns.cloudflare.com
- jason.ns.cloudflare.com
- lauryn.ns.cloudflare.com
- a.share-dns.com
- a9.share-dns.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
- b.share-dns.net
- b9.share-dns.net
Threat-feed evidence
History
Related pages
Pivot from ker3000.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: "ker3000.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.