VirusTotal
18 / 91 engine detections
レポートを開く“Yоutubе | Copyright strikes”
YouTubeなりすまし: sweeply.digital — コンテンツが利用できません. 証拠の概要: VirusTotal 18/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF); URLQuery 3 alerts…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
18 / 91 engine detections
レポートを開く3 threat-system alerts
レポートを開く4/14
悪意あり
レポートを開く1 community reference
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Quad9 DNS | sweeply.digital |
malicious | Sinkholed |
| Hagezi Threat Feed | sweeply.digital |
malicious | Sinkholed |
| DNS4EU | sweeply.digital |
malicious | Sinkholed |
PhishDestroy threat report
This domain, sweeply.digital, was identified as a phishing site designed to mimic YouTube’s copyright strike notification system. The site likely targeted content creators or channel owners by presenting a fraudulent alert about copyright violations, tricking users into entering account credentials or other sensitive information under the guise of resolving a strike. Such tactics exploit urgency and fear, common in credential harvesting campaigns, to bypass rational scrutiny and prompt immediate action from victims. Analysis indicates the domain was registered on January 22, 2026, through NameCheap, Inc., and resolved to the IP address 188.114.97.3, hosted on Cloudflare’s infrastructure (AS13335). At the time of detection, 18 out of 95 security vendors on VirusTotal flagged sweeply.digital as malicious, with no SSL certificate present to encrypt traffic. The page title, "Yоutubе | Copyright strikes," used Unicode characters to visually impersonate the legitimate YouTube brand, a technique known as homograph spoofing. The domain appeared on one security blocklist and was subsequently taken offline, though residual risk remains for users who may have interacted with it prior to deactivation. Individuals who visited sweeply.digital or entered credentials on the site should assume their account information has been compromised. Immediate steps include changing passwords for the affected account and any other platforms where the same credentials were reused. Enable multi-factor authentication (MFA) on all critical accounts to mitigate unauthorized access. Monitor the account for unusual activity, such as unauthorized videos, comments, or settings changes. If financial or personal data was submitted, consider placing a fraud alert with credit bureaus and reviewing transaction histories for signs of misuse. Organizations should update endpoint protection rules to block the domain and its associated IP address, and educate users on recognizing phishing attempts that exploit brand impersonation and urgency.
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.
Edge-IP の評判はこのドメインに起因しません。
grant.ns.cloudflare.comnadia.ns.cloudflare.comLocation describes the IP network.
Saved 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 sweeply.digital · checked Jun 1, 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='sweeply.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
sweeply.digital
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
18/91 engine detections
View source1 community references
View sourceNo threat flag
View sourcesweeply.digital
View sourcePD-20260601-ED5741
コミュニティの 1 人が報告・初回確認 2026年6月1日
PD-20260601-ED5741 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
sweeply.digital)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.