bitget-token[.]cc

PhishDestroy first recorded bitget-token.cc on Sep 16, 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 85/100.

The latest stored availability state is “Content unavailable” on Aug 3, 2026 at 01:09 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.

VirusTotal returned 6 detections from 95 scanners in the stored check on Feb 23, 2026 at 05:37 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 3, 2026 at 02: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 a positive flag on Feb 25, 2026 at 20:32 UTC. AlienVault OTX stored 0 pulse references on Mar 1, 2026 at 23:06 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 14, 2026 at 22:32 UTC. That result is not evidence of safety. A URLScan capture is stored from Mar 5, 2026 at 01:27 UTC.

Stored context lists registrar NameSilo, LLC, IP address 43.212.99.130, registration date Sep 13, 2025, apparent target Bitget. 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.