Hostname
fashiola.de
Last fetched
fashiola.de resolves to 3.161.82.17, announced in 3.161.80.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. fashiola.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
- 3.161.82.17
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.22
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.30
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.85
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.85.65.2
52.85.64.0/22 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 52.85.65.6
52.85.64.0/22 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 52.85.65.68
52.85.64.0/22 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 52.85.65.87
52.85.64.0/22 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for fashiola.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
Showing 4 of 4 subdomains (4 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
- pns51.cloudns.net
- pns52.cloudns.net
- pns53.cloudns.net
- pns54.cloudns.net
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- include: spf.mandrillapp.com
- mx: fashiola.de
Threat-feed evidence
History
Related pages
Pivot from fashiola.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: "fashiola.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.