VirusTotal
4 / 89 engine detections
Відкрити звіт“404 - Страница не найдена”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@beget.ru.
The latest stored availability evidence still shows the domain reachable; 7 months 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.
домен у блоклистах: cssc.report — Неперевірений. Зведення доказів: VirusTotal 4/89 (alphaMountain.ai, Bfore.Ai PreCrime, Chong Lua Dao, Gridinsoft); 1…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
4 / 89 engine detections
Відкрити звітchecked — no detections recorded
Відкрити звітchecked — no match recorded
23 community references
Відкрити звітprovider verdict: clean
Відкрити звіт14 перевірено — блокувань немає
No threat flag
Відкрити звітPage capture
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, cssc.report, is flagged as a generic phishing threat with high risk and remains active as of July 12, 2026. Registered on March 02, 2026, through HOSTINGER operations, UAB, it resolves to IP address 87.236.16.177 located in Russia, hosted on AS198610 (Beget LLC). The domain uses Let's Encrypt SSL (R12) and employs PHP and Nginx technologies. The page title displays a 404 error in Russian ("Страница не найдена"), indicating the content may be hidden or recently taken offline, though the domain itself is still operational. Security intelligence sources show broad concern: VirusTotal reports 4 out of 93 vendors flagging the domain, and it appears on two security blocklists (PhishDestroy and ScamSniffer). AlienVault OTX includes this domain in 23 threat intelligence pulses, suggesting active tracking by multiple security communities. The Gridinsoft trust score is 0 out of 100, reflecting no confidence in the domain's legitimacy. Nameservers (ns1.beget.pro, ns2.beget.pro, ns2.beget.com, ns1.beget.com) are consistent with Beget's infrastructure. While the exact phishing lure or target brand is not identified in the available data, the combination of recent registration, low trust score, multiple blocklist entries, and threat pulse inclusion strongly suggests malicious intent. Defenders should block this domain at network and email gateways, monitor for related subdomains or IP changes, and consider the domain as potentially part of a larger phishing campaign. No further specifics about the page content or scam type are available from the provided intelligence.
Last checked
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
ns1.beget.comLocation describes the IP network.
a3c250917303262eeb9c25294df07e188cc8513f34acf191b1bf52f83e31ba8awww.cssc.reportSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.cssc.reportDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of cssc.report · checked Jul 12, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cssc.report
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
3→4
https://radar.cloudflare.com/scan/8ac4f1c8-4f70-490c-a2cd-fbc16f5a17fb
0→1
23 community references
View source4/89 engine detections
View sourceNo threat flag
View sourcePage captured
View sourcecssc.report
View sourcePD-20260302-CBE6E6
Повідомив 1 учасник спільноти; уперше помічено 02.03.2026
PD-20260302-CBE6E6 Recipient: abuse@beget.ru Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
cssc.report)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.