mx-flow[.]de

PhishDestroy first recorded mx-flow.de on Jul 3, 2026. This English evidence brief is rebuilt from the current structured observations stored for the report. The current evidence score, computed from those stored observations, is 80/100.

The latest stored availability state is “Last known active” (HTTP 301) on Aug 2, 2026 at 10:35 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.

VirusTotal returned 5 detections from 91 scanners in the stored check on Jul 3, 2026 at 12:30 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 2, 2026 at 10:20 UTC. PhishDestroy's own listing is excluded from that count. A zero-match snapshot is not a safety verdict.

Other stored evidence. Google Safe Browsing stored no positive flag on Jul 3, 2026 at 12:25 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Jul 3, 2026 at 12:31 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 3, 2026 at 14:30 UTC. That result is not evidence of safety. A URLScan capture is stored from Jul 3, 2026 at 12:20 UTC.

Stored context lists IP address 213.136.93.167, apparent target Adobe. Except for the registration date, these fields do not share a source timestamp in this report and may change.

Treat these as stored, time-bound observations rather than a live safety guarantee. Source verdicts and reachability can change, and zero or missing vendor matches never prove that a domain is safe. Avoid interacting with the domain while uncertainty remains, and use the appeal process if this report is inaccurate.