Hostname
refluenced.de
Last fetched
refluenced.de resolves to 108.159.80.128, announced in 108.159.80.0/24 by AMAZON-02 - Amazon.com, Inc. in IN. refluenced.de 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
- 108.159.80.128
108.159.80.0/24 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 108.159.80.48
108.159.80.0/24 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 108.159.80.65
108.159.80.0/24 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 108.159.80.85
108.159.80.0/24 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 52.85.61.117
52.85.61.0/24 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.85.61.47
52.85.61.0/24 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.85.61.61
52.85.61.0/24 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.85.61.66
52.85.61.0/24 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for refluenced.de is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for refluenced.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
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
- ns-271.awsdns-33.com
- ns-515.awsdns-00.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-1437.awsdns-51.org
- ns-1668.awsdns-16.co.uk
Threat-feed evidence
History
Related pages
Pivot from refluenced.de 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: "refluenced.de"})-[: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.