Hostname
fusd.net
Last fetched
fusd.net resolves to 104.17.71.73, announced in 104.17.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. fusd.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.17.71.73
104.17.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for fusd.net is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:9
- Registrant organisation
- perfect privacy,
- Contact emails
- 06f8d42e0a28fd0a4b5550a3a3fa3dbf@domaindiscreet.com, 0ed144c40a28fd0a634955e22578c942@domaindiscreet.com, 0f5d11930a28fd0a4a0d851e75d1af5c@domaindiscreet.com, 19ca69bd0a28fd0a46b0717992f98cbb@domaindiscreet.com, 2c1443430a28fd0a3ce3eda6312d35e5@domaindiscreet.com, 368676190a28fd0a1bbbefeacf36776f@domaindiscreet.com, 3ac1c94d0a16123348cc9f2912816a77@domaindiscreet.com, 58055719@myprivatename.com, 615b6b240a28fd0a3c849be8ba60a82e@domaindiscreet.com, 7b7e4a180a28fd0a305abc5fc3356507@domaindiscreet.com, 906268200a28fd0a157052cba6ed5519@domaindiscreet.com, a9ab65ae0a28fd0a346633b55380b78c@domaindiscreet.com, bf9f40830a28fd0a41b091cc0d5dc973@domaindiscreet.com, dgg9euqcqci8l8k1cr7mpjabua@domaindiscreet.com, e3aad3e70a28fd0a1957de74fad71767@domaindiscreet.com
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns1-09.azure-dns.com
- ns4-09.azure-dns.info
- ns2-09.azure-dns.net
- ns3-09.azure-dns.org
MX records
- fusd-net.mail.protection.outlook.com
SPF policy
- ip: 208.64.34.39/32
- ip: 208.64.34.43/32
- ip: 208.64.34.96/32
- include: spf.protection.outlook.com
- a: fusd.net
- mx: fusd.net
Threat-feed evidence
History
Related pages
Pivot from fusd.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: "fusd.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.