binance-authenticate[.]com

PhishDestroy first recorded binance-authenticate.com on Jul 10, 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 95/100.

The latest stored availability state is “Last known active” on Aug 2, 2026 at 00:13 UTC. No conclusive HTTP response is stored, so current availability remains unverified.

VirusTotal returned 10 detections from 91 scanners in the stored check on Jul 10, 2026 at 19:12 UTC. The independent blocklist snapshot recorded 2 matches (MetaMask, SEAL) across 10 configured external sources on Aug 2, 2026 at 00:20 UTC. PhishDestroy's own listing is excluded from that count.

Other stored evidence. Google Safe Browsing stored no positive flag on Jul 10, 2026 at 16:54 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 1 pulse reference on Jul 10, 2026 at 16:50 UTC. OTX pulses are community-intelligence references, not vendor verdicts. Spamhaus DBL stored the result DBL_PHISH on Jul 12, 2026 at 16:30 UTC. A URLScan capture is stored from Jul 11, 2026 at 10:12 UTC.

Stored context lists registrar Fewmoretaps OU d/b/a Trustname.com, IP address 139.99.45.145, registration date Jul 8, 2026, apparent target Binance. 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.