Skip to content

Hostname

wortwuchs.net

Last fetched

wortwuchs.net resolves to 104.21.12.237, announced in 104.21.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. wortwuchs.net 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 · wortwuchs.netRouting diversity3.0/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/wortwuchs.net

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:151
Registrant organisation
jonas geldschl?ger
Contact emails
14357b83k96@opensrs.namespace4you.com, h3196403@domains.namespace4you.com

Subdomains

Subdomain
cdn-0.wortwuchs.net
cdn-1.wortwuchs.net
cdn-2.wortwuchs.net
cdn-3.wortwuchs.net
cdn-4.wortwuchs.net
cdn-5.wortwuchs.net
cdn-6.wortwuchs.net
cdn-7.wortwuchs.net
cdn.wortwuchs.net
forum.wortwuchs.net
www.wortwuchs.net

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

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • lindsey.ns.cloudflare.com
  • sevki.ns.cloudflare.com
  • bison.ezoicns.com
  • llama.ezoicns.com
  • okapi.ezoicns.com
  • zebra.ezoicns.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

  • p20.hpress.de

SPF policy

  • include: _spfp20.hpress.de
  • a: wortwuchs.net
  • mx: wortwuchs.net

Threat-feed evidence

History

Related pages

Pivot from wortwuchs.net 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: "wortwuchs.net"})-[: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.