VirusTotal
19 / 89 engine detections
レポートを開く“500 Internal Server Error”
フィッシング: doz.cure-off.shop — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 19/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); CF Radar…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
19 / 89 engine detections
レポートを開く悪意あり
レポートを開くno 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.
PhishDestroy threat report
doz.cure-off.shop is an impersonation phishing page that copies a legitimate service so visitors will trust it with sensitive information. It sits on a throwaway subdomain of a cheap .shop domain, a common setup for short-lived scam pages. PhishDestroy first saw it on 2026-09-12, and it was still online and serving content when last checked on 2026-10-19. Its page title reads "500 Internal Server Error", while our classification is impersonation phishing.
Impersonation pages copy the look of a brand people already trust, such as a wallet, exchange or login portal, and ask for something only the real service should receive. That could be account credentials, one-time codes or a wallet's recovery phrase. Once submitted, the details go straight to the operators, who use them to take over accounts or empty wallets, often within minutes. Victims usually arrive through links in messages, ads or social media posts.
When it was scanned on VirusTotal on 2026-09-20, 19 of 89 engines flagged the domain. The detections come from unrelated vendors: alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker and Fortinet. Agreement across that many independent engines strongly supports the phishing verdict. The domain is also listed on the PhishDestroy blocklist.
The parent domain was registered through Spaceship, Inc. on 2025-11-13, about ten months before PhishDestroy detected this subdomain. A domain held that long before use suggests it was set aside in advance, and the operators can add new subdomains to it whenever they like. The site runs behind Cloudflare, with the address located in Canada, so the real origin server is hidden from view.
If you typed a password on this site, change it right away on the genuine service and anywhere else you reuse it. Then turn on app-based two-factor authentication and review recent logins. If you entered a wallet recovery phrase, treat that wallet as compromised and move any remaining funds to a new wallet created with a fresh phrase. Do not reply to anyone offering to recover your losses, because follow-up recovery scams are common. Security teams should block the domain and its parent cure-off.shop at DNS and proxy level, and report it to Cloudflare and Spaceship for takedown.
For the registrable domain cure-off.shop behind this subdomain, 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 の評判はこのドメインに起因しません。
nico.ns.cloudflare.comLocation describes the IP network.
bca87826cedd35a82969a335fd112a178986b29f5c6aa9e7d22cefafbf94e54fSaved 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 doz.cure-off.shop · checked Sep 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.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
doz.cure-off.shop
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
利用不可→到達可能
到達可能→利用不可
No threat flag
View source19/89 engine detections
View sourcePage captured
View sourcedoz.cure-off.shop
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
doz.cure-off.shop)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.