Hostname
fnze.net
Last fetched
fnze.net resolves to 100.52.76.253, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. fnze.net 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
- 100.52.76.253
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 107.23.152.169
107.23.128.0/17 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.233.132.247
18.232.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 184.72.154.211
184.72.128.0/17 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.230.9.164
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.22.131.98
52.20.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.145.144.182
54.144.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.234.107.192
54.234.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for fnze.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- domain registration
- Contact emails
- 14449904@qq.com, blue088@163.com, domreg@impact.com, owner-2431921@fnze.net.whoisprivacyservice.org
Subdomains
| Subdomain |
|---|
| 50714.fnze.net |
| wildcard.fnze.net |
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns-62.awsdns-07.com
- ns-972.awsdns-57.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
- ns-1355.awsdns-41.org
- ns-1836.awsdns-37.co.uk
Threat-feed evidence
History
Related pages
Pivot from fnze.net 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: "fnze.net"})-[: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.