Hostname
116kan.com
Last fetched
116kan.com resolves to 104.21.51.200, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. 116kan.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.51.200
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.21.85.169
104.21.80.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.233.219.123
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.233.219.49
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.233.219.78
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.25
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.38
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.8
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.67.185.129
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.208.131
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:472
- Registrant organisation
- nanci nette
- Contact emails
- domains@namemanagementgroup.com, whoisprotect@dnspod.com
Subdomains
Mail and authentication
Nameservers
- ns1.abovedomains.com
- 5014.ns1.abovedomains.com
- ns2.abovedomains.com
- 5014.ns2.abovedomains.com
- fattouche.ns.cloudflare.com
- nova.ns.cloudflare.com
- rommy.ns.cloudflare.com
- tessa.ns.cloudflare.com
- ns1.parklogic.com
- ns2.parklogic.com
MX records
- park-mx.above.com
- mx156.hostedmxserver.com
SPF policy
- ip: fdcf:abda:4154::/48
Threat-feed evidence
History
Related pages
Pivot from 116kan.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: "116kan.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.