VirusTotal
11 / 92
“kraken”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse-reports@cloudzy.com.
The latest stored availability evidence still shows the domain reachable; 16 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
slon3ccticket.ru — Останній відомий активний (HTTP 200). Уособлення бренду: Kraken; Тип шахрайства: Impersonation. Зведення доказів: VirusTotal 11/92 (alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet); URLQuery 2 det.; PhishDestroy score 98/100. Реєстратор: REGRU-RU.
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
11 / 92
2 det.
Повідомити4 community references
Повідомитиprovider verdict: clean
Повідомитизбережений звіт
Повідомити Аналіз завершено
ПовідомитиChecked; no threat flag recorded
Повідомитиslon3ccticket.ru returned HTTP status 200 in an HTTP check recorded on 2026-10-01, according to the evidence set. The domain was first observed on 2026-09-25, and a PhishDestroy internal listing is recorded as true.
The HTTP check dated 2026-10-01 recorded status 200 for slon3ccticket.ru. The first observation of the domain is dated 2026-09-25, and the PageSpeed check on that same date recorded a performance score of 100. VirusTotal, checked on 2026-09-27, reported 7 detections across 91 scanners. OTX, also checked on 2026-09-27, recorded 4 pulses. The registration date is 2026-03-15 with registrar REGRU-RU, and the resolved IP address 104.194.143.10 is recorded in GB.
The recorded sources describe different aspects of slon3ccticket.ru rather than a single measurement. The HTTP response, PageSpeed score, VirusTotal detections, OTX pulses, and the PhishDestroy listing each come from separate checks, so their values should be read individually. The chronology from first observation to the later checks is short, and the exact dates allow a reader to see which records were captured before others without treating that order as a trend.
For slon3ccticket.ru, preserve the HTTP check record, the PhishDestroy internal listing, and the VirusTotal and OTX results as separate items. Compare the HTTP response record against the first-observation record in one review, and compare the VirusTotal and OTX records against each other in a separate review. Retain the PageSpeed record alongside these so future checks can be lined up against the same source set.
Збережені дані спостережень за взаємодією веб-сканера та браузера для цього хоста, а також перевірка відбитків у режимі реального часу для систем розподілу трафіку типу «Кейтаро».
nginxПримітка щодо сканера: alive_content: raw=ok; http=200; via=https_proxy; server=nginx
keenan.ns.cloudflare.comsunny.ns.cloudflare.comLocation describes the IP network.
9acc9eb266bbb24c315534b758dadfbcca09704175a123425c492ccb621da741Saved 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 slon3ccticket.ru · checked Sep 25, 2026
104.194.143.10. 14 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 схожих доменів
Показано 100 із 114
PD-20260925-045C1C Recipient: abuse-reports@cloudzy.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога