Hostname
fndkai.com
Last fetched
fndkai.com resolves to 104.18.4.19, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. fndkai.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.18.4.19
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.5.19
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 199.91.74.172
199.91.74.0/24 · ZEN-ECN - Zenlayer Inc · Mexico City, MX
- 199.91.74.174
199.91.74.0/24 · ZEN-ECN - Zenlayer Inc · Mexico City, MX
- 223.119.40.143
223.119.40.0/22 · CMI-INT-HK - China Mobile International Limited
- 223.119.40.145
223.119.40.0/22 · CMI-INT-HK - China Mobile International Limited
- 98.98.253.35
98.98.253.0/24 · ZEN-ECN - Zenlayer Inc · Mexico City, MX
- 98.98.253.82
98.98.253.0/24 · ZEN-ECN - Zenlayer Inc · Mexico City, MX
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1923
Subdomains
| Subdomain |
|---|
| api.fndkai.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns1.huaweicloud-dns.cn
- ns1.huaweicloud-dns.com
- ns1.cloudflare.net
- ns2.cloudflare.net
- ns3.cloudflare.net
- ns4.cloudflare.net
- ns5.cloudflare.net
- ns1.huaweicloud-dns.net
- 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.huaweicloud-dns.org
Threat-feed evidence
History
Related pages
Pivot from fndkai.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: "fndkai.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.