Hostname
deep-edge.cc
Last fetched
deep-edge.cc resolves to 104.21.50.146, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. deep-edge.cc is listed by 4 threat feeds; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 4 threat feeds. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 4
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:45:21 GMT
- Last seen on a feed
- Tue, 22 Sep 2026 00:51:35 GMT
Nutrition Label
Resolution chain
- 104.21.50.146
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.207.3
172.67.192.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.233.211.57
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.61.123
172.239.32.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.233.211.67
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for deep-edge.cc. 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.
Subdomains
| Subdomain |
|---|
| www.deep-edge.cc |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- anita.ns.cloudflare.com
- pete.ns.cloudflare.com
- ns1.parklogic.com
- ns2.parklogic.com
MX records
- mx156.hostedmxserver.com
Threat-feed evidence
History
Related pages
Pivot from deep-edge.cc 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: "deep-edge.cc"})-[: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.