aml-check[.]github[.]io

PhishDestroy first recorded aml-check.github.io on May 29, 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 45/100.

The latest stored availability state is “Content unavailable” (HTTP 404) on Aug 1, 2026 at 03:00 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.

VirusTotal returned 0 detections from 91 scanners in the stored check on Jul 18, 2026 at 22:45 UTC. A zero-vendor result is not a safety verdict. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 2, 2026 at 00: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 May 29, 2026 at 19:57 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on May 30, 2026 at 01:11 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 13, 2026 at 16:34 UTC. That result is not evidence of safety. A URLScan capture is stored from Jun 25, 2026 at 10:23 UTC.

Stored context lists registrar GitHub, Inc., IP address 185.199.110.153, registration date Mar 10, 2026, apparent target AML Scam. 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.