Skip to content

Hostname

mdrza.de

Last fetched

mdrza.de resolves to 104.26.8.56, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. mdrza.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 · mdrza.deRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/mdrza.de

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mdrza.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
api.mdrza.de
blog.mdrza.de
develop.mdrza.de
gs.mdrza.de
li191.mdrza.de
sms.mdrza.de
stage-verwaltung.mdrza.de
stage.mdrza.de
stats.mdrza.de
verwaltung.mdrza.de
www.mdrza.de

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

  • chad.ns.cloudflare.com
  • lady.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

  • mgks.kreativstrecke.net

SPF policy

  • include: _spf.aok.de
  • a: mdrza.de
  • mx: mdrza.de
  • a: blog.mdrza.de
  • include: _spf.kreativstrecke.net

Threat-feed evidence

History

Related pages

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