hally[.]ws

PhishDestroy first recorded hally.ws on May 1, 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 98/100.

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

VirusTotal returned 11 detections from 91 scanners in the stored check on Aug 1, 2026 at 02:50 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 5, 2026 at 18: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 26, 2026 at 04:18 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on May 1, 2026 at 19:57 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 13, 2026 at 14:38 UTC. That result is not evidence of safety. A URLScan capture is stored, but no capture timestamp is available.

Stored context lists IP address 109.120.156.136, apparent target Across. 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.