Skip to content

Hostname

medimax.de

Last fetched

medimax.de resolves to 3.68.136.240, announced in 3.64.0.0/12 by AMAZON-02 - Amazon.com, Inc. in DE. medimax.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 · medimax.deRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/medimax.de

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for medimax.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
aktion.medimax.de
cd.medimax.de
cdn.medimax.de
hw-new-dev.medimax.de
karriere.medimax.de
news.medimax.de
old.medimax.de
prospekt.medimax.de
testkarriere.medimax.de
universalapp.medimax.de
www.medimax.de

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

  • ns2.xc-ns.de
  • ns5.xc-ns.de
  • ns-2029.awsdns-61.co.uk

MX records

  • gw000219-eu.fortimail.com

SPF policy

  • ip: 213.61.90.128/25
  • ip: 194.55.3.219/32
  • ip: 20.107.242.47/32
  • include: spf.imc-hosting.com
  • include: spf.protection.outlook.com
  • a: medimax.de
  • mx: medimax.de
  • a: reklamekontor-hetzner2.saltation.de
  • include: servers.mcsv.net

Threat-feed evidence

History

Related pages

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