VirusTotal
5 / 91
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“kraken-zerkalo.co | 522: Connection timed out”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
5 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
3 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
kraken-zerkalo.co returned HTTP status 301 on 2026-10-01, according to the recorded HTTP check. A PhishDestroy internal listing for the domain was also recorded, marking it in that publisher-owned catalogue.
The HTTP check on 2026-10-01 recorded status 301 at IP address 172.67.204.3, associated with Cloudflare, Inc. in CA. VirusTotal recorded 4 detections across 91 scanners on 2026-10-01. The OTX check on 2026-09-29 returned 3 pulses. A PhishDestroy internal listing for kraken-zerkalo.co was recorded. The domain was first observed on 2026-09-25, and an SSL scan on 2026-09-25 named Let's Encrypt / YE2 as the issuer.
The PhishDestroy listing and the OTX pulses are separate source records, so each should be read on its own terms rather than merged. The HTTP 301 and the VirusTotal result share a calendar date, but that alone does not establish that the two checks were performed simultaneously or that they describe the same content. The first observation and the SSL scan also share a date, which shows only that both records were captured then.
Preserve the PhishDestroy listing and the OTX pulse record as separate source records for kraken-zerkalo.co. Compare the HTTP response record with the VirusTotal result in separate sentences, since each captures a different kind of observation. Retain the first-observed record alongside the later checks so the chronology of the recorded sources remains intact. Review the recorded HTTP 301 as describing only the recorded response, not all content the domain may serve.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://kraken-zerkalo.co/; server=cloudflare
Edge-IP reputation is not attributed to this domain.
ximena.ns.cloudflare.comLocation describes the IP network.
04ed5a01b9e82e2a7da53a04c04e2bad91e46e2bcd6146ed8073e4fc42efcffeSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
172.67.204.3.13 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.
114 stored lookalike domains
Showing 100 of 114
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