VirusTotal
18 / 89 engine detections
レポートを開く“Home - wuzyree”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
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.
Wordpressなりすまし: wuzyree.com — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 18/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLQuery 4…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
18 / 89 engine detections
レポートを開く4 threat-system alerts
レポートを開く悪意あり
レポートを開く5 community references
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | wuzyree.com |
malicious | Sinkholed |
| Cloudflare DNS | wuzyree.com |
malicious | Sinkholed |
| Quad9 DNS | wuzyree.com |
malicious | Sinkholed |
| DNS4EU | wuzyree.com |
malicious | Sinkholed |
PhishDestroy threat report
wuzyree.com is an impersonation phishing page, a site built to pass itself off as a service people already trust so they hand over credentials, payment details or funds. PhishDestroy first flagged it on 2026-09-19. The site has been offline since 2026-09-21, and as of 2026-10-19 it remains dead with its content blocked at the provider.
Impersonation sites copy the look, wording and flow of a real brand, then wait for visitors arriving from ads, search results, direct messages or lookalike links. The victim believes they are logging in, verifying an account or completing a transaction. Whatever they type goes to the operators, who use it to take over accounts or move money. The browser tab read only "Home - wuzyree", a generic default that names the site itself rather than any brand, while our classification rests on the page's impersonation behaviour.
Eighteen of 89 VirusTotal engines flagged the domain in a check on 2026-09-21. That is a solid independent signal for a site that lived only a few days after detection. The vendors include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, CyRadar and the Vietnamese anti-phishing group Chong Lua Dao. The domain also appears in five AlienVault OTX threat pulses, so other researchers have tracked it as well. PhishDestroy lists it on its blocklist.
The domain was registered through NAMECHEAP INC on 2026-06-03, roughly three and a half months before PhishDestroy caught it. That gap suggests a domain held in reserve or used quietly before the campaign surfaced. It resolved to 188.114.96.3, an address located in the US. Its certificate came from Google Trust Services (WE1), so the padlock in the address bar said nothing about whether the site was safe.
If you entered a password on wuzyree.com, change it on the real service and on any other account that shares it. Turn on app-based two-factor authentication and review recent logins for sessions you don't recognise. If you submitted card or bank details, contact your bank to block the card and dispute charges. If you typed a wallet recovery phrase, treat that wallet as compromised and move the funds to a newly created wallet at once. Defenders should block the domain and its IP at the DNS and proxy level and search mail and web logs for users who reached it around 2026-09-19 to 2026-09-21.
Edge-IP の評判はこのドメインに起因しません。
amber.ns.cloudflare.comdamien.ns.cloudflare.comLocation describes the IP network.
a8071a25039e64b7a59a9b71fadf22f56f738de8ab752e06e3a6ad879578f074Saved 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 wuzyree.com · checked Sep 19, 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
wuzyree.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
5 community references
View sourceNo threat flag
View source18/89 engine detections
View sourcePD-20260919-2C15AA
Page captured
View sourcewuzyree.com
View sourcePD-20260919-2C15AA 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 ↗
wuzyree.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.