Skip to content

Hostname

berghupfer.de

Last fetched

berghupfer.de resolves to 185.243.11.29, announced in 185.243.11.0/24 by netcup-AS - netcup GmbH in DE. berghupfer.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 · berghupfer.deRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.2/10canon.whisper.security/host/berghupfer.de

Resolution chain

IPv6 resolution

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

Attribution

netcup

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for berghupfer.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
ftp.berghupfer.de
hafen.berghupfer.de
mail.berghupfer.de
om.berghupfer.de
pop.berghupfer.de
replay.berghupfer.de
staging.berghupfer.de
stats.berghupfer.de
webmail.berghupfer.de
wf1.berghupfer.de
www.berghupfer.de

Showing 11 of 15. 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

  • ns5.kasserver.com
  • ns6.kasserver.com
  • root-dns.netcup.net
  • second-dns.netcup.net
  • third-dns.netcup.net

MX records

  • w02134a5.kasserver.com
  • mail.berghupfer.de
  • rw0b1d.webhosting.systems

SPF policy

  • include: spf.kasserver.com
  • a: berghupfer.de
  • mx: berghupfer.de
  • include: _spf.webhosting.systems

Threat-feed evidence

History

Related pages

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