japi-trust[.]github[.]io

PhishDestroy first recorded japi-trust.github.io on Jun 20, 2026. This English evidence brief is rebuilt from the current structured observations stored for the report. The current stored risk score is 70/100.

The latest stored availability state is “Content unavailable” (HTTP 404) on Aug 1, 2026 at 03:03 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 18, 2026 at 20:45 UTC. 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 Jun 20, 2026 at 14:30 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Jun 20, 2026 at 14:30 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 20, 2026 at 20:30 UTC. That result is not evidence of safety. A URLScan capture is stored from Jun 24, 2026 at 10:13 UTC.

Stored context lists registrar GitHub, Inc., IP address 185.199.109.153, registration date Feb 22, 2022, apparent target Apple. 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.