Skip to content

Hostname

falstaff.de

Last fetched

falstaff.de resolves to 84.242.9.28, announced in 84.242.8.0/21 by NESSUS - Nessus GmbH in AT. falstaff.de is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · falstaff.deRouting diversity1.5/10Peering density7.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/falstaff.de

Resolution chain

IPv6 resolution

No AAAA record for falstaff.de is recorded in WhisperGraph.

Attribution

nessus

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for falstaff.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

Subdomain
backend.falstaff.de
barvoting.falstaff.de
data-9fcd0b641d.falstaff.de
fhcshop.falstaff.de
shop.falstaff.de
voting.falstaff.de
weinbarvoting.falstaff.de
www.falstaff.de

Showing 8 of 9. View all 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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.konzept.cc
  • ns2.konzept.cc
  • ns3.konzept.cc

MX records

  • falstaff-de.mail.protection.outlook.com

SPF policy

  • ip: 193.104.82.0/24
  • ip: 85.126.200.0/27
  • ip: 213.229.2.64/27
  • include: spf.konzept.cc
  • include: spf.mailjet.com
  • include: spf.protection.outlook.com
  • include: shops.shopify.com
  • include: servers.mcsv.net
  • ip: 91.250.83.165

Threat-feed evidence

History

Related pages

Pivot from falstaff.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: "falstaff.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.