Skip to content

Hostname

witze-paradies.de

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for witze-paradies.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
1f83ce0a919e.witze-paradies.de
www.witze-paradies.de

Showing 2 of 3. 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

Mail and authentication

Nameservers

  • rajeev.ns.cloudflare.com
  • sharon.ns.cloudflare.com
  • 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

MX records

  • spanel-108758.spanel.io
  • mx001.cloudeu.xion.oxcs.net
  • mx002.cloudeu.xion.oxcs.net
  • mx003.cloudeu.xion.oxcs.net
  • mx004.cloudeu.xion.oxcs.net

SPF policy

  • a: witze-paradies.de
  • mx: witze-paradies.de
  • include: xcloud.email
  • ip: 162.55.214.226

Threat-feed evidence

History

Related pages

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