Hostname
fury.io
Last fetched
fury.io resolves to 3.217.47.240, announced in 3.208.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. fury.io 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
- 3.217.47.240
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.226.149.3
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.226.43.197
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.93.223.26
3.80.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.235.85.56
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.194.249.73
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.160.224.51
54.160.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.197.115.33
54.196.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.227.151.68
54.226.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.90.56.85
98.88.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.85.21.182
98.80.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.50.188.91
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
- 2600:1f10:49e5:2f04:6508:acf:630d:9215
- 2600:1f10:49e5:2f05:c662:edd6:c059:d79a
- 2600:1f10:49e5:2f06:1392:2c39:563a:3921
- 2600:1f18:576b:3004:3e7e:781c:9311:ad56
- 2600:1f18:576b:3005:6351:e97d:1790:3aa3
- 2600:1f18:576b:3006:40c1:1013:74a1:657d
- 2600:1f18:677:2304:5282:7fe3:c4a8:6241
- 2600:1f18:677:2305:14ef:a8a5:e8ae:3742
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
Subdomains
Mail and authentication
Nameservers
- ns-155.awsdns-19.com
- ns-1004.awsdns-61.net
- ns-1027.awsdns-00.org
- ns-1872.awsdns-42.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
Threat-feed evidence
History
Related pages
Pivot from fury.io 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: "fury.io"})-[: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.