Hostname
fluxpools.net
Last fetched
fluxpools.net resolves to 104.21.37.241, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. fluxpools.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
- 104.21.37.241
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.215.132
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1327
- Registrant organisation
- registration privacy, no-ip.com
- Contact emails
- 18ad92366f3c4021-1095894@privacy.no-ip.com, 193f5b36de168bb8-1095894@privacy.no-ip.com, 2ef0561355d11c24-1095894@privacy.no-ip.com, 399bbb5c876d538b-1095894@privacy.no-ip.com, 45d6315fdf3b82a2-1095894@privacy.no-ip.com, 6faa1a6bae17b265-1095894@privacy.no-ip.com, 74b213de970b824e-1095894@privacy.no-ip.com, 8220164d5ae4bd81-1095894@privacy.no-ip.com, 9a202f7b6041542a-1095894@privacy.no-ip.com, 9ef1690f2b17dd7d-1095894@privacy.no-ip.com, af740de9a92bb611-1095894@privacy.no-ip.com, c438bc3d23d6056f-1095894@privacy.no-ip.com, cb608a488b30c1a9-1095894@privacy.no-ip.com, d3b45255bf97fc3e-1095894@privacy.no-ip.com, da5a58839c05922e-1095894@privacy.no-ip.com, efde4be68438dfcc-1095894@privacy.no-ip.com
Subdomains
| Subdomain |
|---|
| api-flux.fluxpools.net |
| api-soloflux.fluxpools.net |
| dev.fluxpools.net |
| fluxtest.fluxpools.net |
| soloflux.fluxpools.net |
| test-flux.fluxpools.net |
| test.fluxpools.net |
| zel.fluxpools.net |
Showing 8 of 8 subdomains (8 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
- igor.ns.cloudflare.com
- janet.ns.cloudflare.com
Threat-feed evidence
History
Related pages
Pivot from fluxpools.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: "fluxpools.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.