Hostname
dealkenya.com
Last fetched
dealkenya.com resolves to 104.21.45.177, announced in 104.21.96.0/19 by CLOUDFLARENET - Cloudflare, Inc. in CA. dealkenya.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
- 104.21.45.177
104.21.96.0/19 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 13.35.58.120
13.35.62.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.35.58.123
13.35.62.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.35.58.13
13.35.62.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.35.58.98
13.35.62.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 172.67.217.182
172.68.10.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1466
- Registrant organisation
- domain name brand company
- Contact emails
- 1fhj@privacy.domainnamebrandcompany.com, festow32@gmail.com, b9a86dc0f1414c2d8c96bb6e0c871cdf.protect@withheldforprivacy.com, cac089e7fcaa402b9f91fc9e22a865f4.protect@withheldforprivacy.com
Subdomains
Showing 2 of 2 subdomains (2 per page).
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
- ara.ns.cloudflare.com
- tom.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
MX records
- route1.mx.cloudflare.net
- route2.mx.cloudflare.net
- route3.mx.cloudflare.net
SPF policy
- include: _spf.mx.cloudflare.net
Threat-feed evidence
History
Related pages
Pivot from dealkenya.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: "dealkenya.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.