jumpbit[.]io

PhishDestroy first recorded jumpbit.io on Dec 3, 2025. 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 65/100.

The latest stored availability state is “Reachable · access restricted” (HTTP 403) on Aug 3, 2026 at 10:24 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.

VirusTotal returned 1 detection from 91 scanners in the stored check on Jul 14, 2026 at 01:00 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 3, 2026 at 14: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 Mar 2, 2026 at 20:41 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Mar 1, 2026 at 15:54 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 14, 2026 at 14:36 UTC. That result is not evidence of safety. A URLScan capture is stored from Feb 27, 2026 at 01:21 UTC.

Stored context lists registrar HOSTINGER operations, UAB, IP address 216.198.79.1, registration date Sep 13, 2025, apparent target Jito. 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.