VirusTotal
6 / 89 engine detections
レポートを開く“Проверка браузера”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@registrar.eu.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
Googleなりすまし: slou2.cc — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 6/89 (alphaMountain.ai, Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Gridinsoft)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 89 engine detections
レポートを開くScan report
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
slou2.cc is an impersonation phishing site that greets visitors with a Russian-language page titled "Проверка браузера" ("Browser check"). PhishDestroy first flagged it on 2026-09-07. It was still online and serving content when last checked on 2026-10-19, so anyone landing there now meets the live page. The page title shows a generic browser-verification screen, while our classification is impersonation phishing.
Impersonation pages borrow the look and wording of a service the victim already trusts so the request that follows feels routine. A "browser check" screen fits that pattern because people are used to clicking through such prompts without thinking. Once past it, a victim of this kind of scheme is typically asked to sign in, verify an account or confirm payment details. Whatever is typed goes straight to the operators, who can then take over the real account or move any funds it controls.
On 2026-09-18, 6 of 89 VirusTotal engines marked the domain as malicious: alphaMountain.ai, Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a small share of engines, so many browsers and filters will not warn about it yet. The vendors that do flag it include predictive and threat-intel services, which tend to catch new phishing before mainstream lists. The domain also appears in 4 AlienVault OTX threat pulses and is listed on the PhishDestroy blocklist.
The domain was registered on 2026-02-25 through Hosting Concepts B.V. d/b/a Registrar.eu. It went undetected for more than six months before PhishDestroy flagged it, which suggests it was registered well ahead of use. Traffic runs through Cloudflare, Inc., geolocated to Canada, which hides the actual origin server. The Let's Encrypt certificate gives it a browser padlock, but that only means the connection is encrypted, not that the site is legitimate.
Do not click through the "browser check" or enter anything on slou2.cc. If you already typed a password there, change it immediately on the real service and on any account that shares it. Turn on app-based two-factor authentication and review recent logins and payments for activity you do not recognize. If you entered card details, contact your bank, and never type a wallet recovery phrase into any page that reached you this way. Defenders should block the domain at DNS and proxy level and alert users to fake browser-verification screens.
Edge-IP の評判はこのドメインに起因しません。
chad.ns.cloudflare.comzoe.ns.cloudflare.comLocation describes the IP network.
6232e9b83ab4196ad784298140085da5bf2701ccbb663ed1c684eca3820daa1dSaved 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 slou2.cc · checked Sep 7, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=Caddy
slou2.cc
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
6→7
5→6
0→5
到達可能
4 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcePD-20260906-FD2F7B
slou2.cc
View sourcePage captured
View sourcePD-20260906-FD2F7B Recipient: abuse@registrar.eu アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
slou2.cc)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.