VirusTotal
3 / 91
On 2026-10-01, tor.blacksprut.org returned an HTTP 502 status during a recorded check, a specific server response at that time. The domain also appears in the PhishDestroy internal listing, and its first observation was recorded on 2026-09-25.
The HTTP status 502 for tor.blacksprut.org was recorded on 2026-10-01. VirusTotal, checked on 2026-09-29, reported 3 detections across 91 scanners. The PhishDestroy internal listing records the domain, and the first observation date is 2026-09-25. A PageSpeed performance score of 100 was measured on 2026-09-25.
The HTTP, VirusTotal, PhishDestroy and PageSpeed records each describe a separate dated observation of tor.blacksprut.org. The HTTP code documents only the response captured at its check time, while the VirusTotal detections and PhishDestroy listing reflect what those sources recorded. Because the dates differ, the records are not directly comparable as a single measurement.
Preserve the HTTP response record and the VirusTotal detection record for tor.blacksprut.org for later comparison. Retain the PhishDestroy listing and the PageSpeed performance score as separate dated references. Compare each source record against its own future observations rather than merging them.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: transient_502: raw=transient_502; http=502; via=http_proxy
ns2.park-my-domain.netLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of tor.blacksprut.org · checked Sep 25, 2026
157.90.33.74. 17 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive