Skip to content

Hostname

manhenke.de

Last fetched

manhenke.de resolves to 104.26.4.74, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. manhenke.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 · manhenke.deRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.2/10canon.whisper.security/host/manhenke.de

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for manhenke.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
karriere.manhenke.de
linke.manhenke.de
mailing.manhenke.de
newsletter.manhenke.de
shop.manhenke.de
stylebox.manhenke.de
www.manhenke.de

Showing 7 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

  • andy.ns.cloudflare.com
  • kimora.ns.cloudflare.com
  • ns1.hosting.de
  • ns2.hosting.de
  • ns3.hosting.de

MX records

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

SPF policy

  • include: spf.crsend.com
  • include: inxserver.com
  • include: spf.protection.outlook.com
  • include: spf.hosting.de
  • a: manhenke.de
  • mx: manhenke.de
  • a: shop.manhenke.de
  • a: manhenke.modehaus.de
  • ip: 93.89.4.194

Threat-feed evidence

History

Related pages

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