VirusTotal
7 / 89
“krab1-cc-onion.ru | 522: Connection timed out”
On 2026-10-01, krab1-cc-onion.ru returned an HTTP 200 status, indicating a successful response to a web request on that date. The domain was also observed in the PhishDestroy internal listing, which is maintained by the publisher.
VirusTotal checked krab1-cc-onion.ru on 2026-09-18 and recorded 7 detections out of 89 scanners. OTX noted 3 pulses for the domain as of 2026-09-11. The SSL certificate was issued by Google Trust Services / WE1, with scanning performed on 2026-09-05.
The evidence from VirusTotal, OTX, and PhishDestroy provides multiple perspectives on krab1-cc-onion.ru, each recorded at different dates. Comparing these sources allows for a broader understanding of the domain's status and potential risks, but the varied observation times mean that conditions may have changed between checks.
To ensure thorough review, retain all evidence related to krab1-cc-onion.ru and compare future observations to these dated records. Avoid submitting sensitive information to the domain during ongoing evaluation, and consult updated sources to track any changes in its status.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='krab1-cc-onion.ru', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
f482e35cdfa67c5060bd5027395bd91c2bfda8cfa536d3aef30ee16ba34b2abfSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
172.67.208.191. 11 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