Hostname
fanczs.com
Last fetched
fanczs.com resolves to 104.126.37.131, announced in 104.126.36.0/23 by AKAMAI-ASN1 - Akamai International B.V. in DE. fanczs.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.126.37.131
104.126.36.0/23 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 104.126.37.176
104.126.36.0/23 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 2.21.33.25
2.21.33.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Prague, CZ
- 2.21.33.9
2.21.33.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Prague, CZ
- 23.212.110.112
23.212.110.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Prague, CZ
- 23.212.110.42
23.212.110.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Prague, CZ
- 23.223.245.36
23.223.245.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Kolkata, IN
- 23.223.245.42
23.223.245.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Kolkata, IN
- 23.36.162.197
23.36.162.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 23.36.162.210
23.36.162.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for fanczs.com is recorded in WhisperGraph.
Attribution
akamai international
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1331
Subdomains
| Subdomain |
|---|
| feilian.fanczs.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns1.alidns.com
- ns2.alidns.com
- vip3.alidns.com
- vip4.alidns.com
- n0a.akamaiedge.net
- n1a.akamaiedge.net
- n2a.akamaiedge.net
- n3a.akamaiedge.net
- n4a.akamaiedge.net
- n5a.akamaiedge.net
- n6a.akamaiedge.net
- n7a.akamaiedge.net
MX records
- m1.feishu.cn
SPF policy
- include: _netblocks.m.feishu.cn
Threat-feed evidence
History
Related pages
Pivot from fanczs.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: "fanczs.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.