torconnect[.]io

PhishDestroy first recorded torconnect.io on May 22, 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 71/100.

The latest stored availability state is “Cloaked · reachable” on Aug 5, 2026 at 01:13 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.

VirusTotal returned 4 detections from 91 scanners in the stored check on May 24, 2026 at 03:02 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 5, 2026 at 10: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 22, 2026 at 08:14 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on May 22, 2026 at 08:15 UTC. OTX pulses are community-intelligence references, not vendor verdicts. Spamhaus DBL stored the result DBL_PHISH on Jul 13, 2026 at 14:35 UTC. A stored Cloudflare Radar snapshot labels the domain malicious. No source check timestamp is stored for this field. A URLScan capture is stored, but no capture timestamp is available.

Stored context lists registrar TUCOWS.COM, CO., IP address 64.29.17.65, registration date May 22, 2026. 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.