VirusTotal
13 / 89 engine detections
レポートを開く“403 Forbidden”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@ownregistrar.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.
Cryptocomなりすまし: onchain-deskcryptohelps.com — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 13/89 (BitDefender, ESET, Emsisoft, Forcepoint ThreatSeeker…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 89 engine detections
レポートを開く15/100
レポートを開く悪意あり
レポートを開くchecked — no detections recorded
レポートを開く5 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
onchain-deskcryptohelps.com is an impersonation phishing page that poses as Crypto.com and targets the exchange's customers and wallet users. Its name dresses it up as an on-chain help desk, a framing meant to catch people who are already looking for support. PhishDestroy first flagged it on 2026-09-13, and as of 2026-10-19 the site was still online and serving content.
Fake support pages like this one borrow Crypto.com's branding and promise to fix a frozen account, a stuck transaction or a verification problem. The victim is then asked to sign in, hand over a 2FA code or recovery phrase, or connect a wallet. Whatever is entered goes straight to the operators, who use it to empty the exchange account or the wallet. The page title reads "403 Forbidden," while scanners matched the content to Crypto.com and we classify it as impersonation phishing.
On 2026-09-14, 13 of 89 VirusTotal engines flagged the domain, including BitDefender, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That is a minority of engines, but the vendors that flagged it are established ones. urlscan.io returned a malicious verdict and independently detected Crypto.com branding on the page. MetaMask and SEAL list the domain alongside PhishDestroy, and five AlienVault OTX pulses reference it. Several unrelated sources reached the same conclusion.
The domain was registered through OwnRegistrar, Inc. on 2026-09-11, only two days before PhishDestroy detected it. That short gap fits a site set up to run a campaign right away. Traffic passes through Cloudflare, Inc. at an address geolocated to Canada, which hides the actual origin server. The Let's Encrypt certificate gives the page a padlock, but that only means the connection is encrypted. It does not show that the site belongs to Crypto.com.
If you entered Crypto.com credentials here, change your password from the official app immediately, reset 2FA, and review recent logins, withdrawals and whitelisted addresses. If you shared a recovery phrase, treat that wallet as compromised and move your funds to a new wallet created on a clean device. If you connected a wallet or signed anything, revoke token approvals with a trusted approval-checker and contact Crypto.com support only through the official app. Security teams should block the domain at DNS and proxy level and add it to mail filters, since links to fake support desks often spread through email, direct messages and search ads.
Last checked
Edge-IP の評判はこのドメインに起因しません。
adaline.ns.cloudflare.comarmfazh.ns.cloudflare.commx.zoho.compriority 10mx2.zoho.compriority 20mx3.zoho.compriority 50Location describes the IP network.
6dc8fd16e59a39188d1103f937113c89ac6995542139c2270eec8184898706adSaved 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 onchain-deskcryptohelps.com · checked Sep 13, 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
onchain-deskcryptohelps.com
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
利用不可→到達可能
不明→inactive
parked · parking_or_lifecycle_page
不明→inactive
parked · parking_or_lifecycle_page
不明→inactive
parked · parking_or_lifecycle_page
到達可能→利用不可
到達可能→利用不可
到達可能
5 community references
View sourceNo threat flag
View source13/89 engine detections
View sourcePD-20260913-1E9075
onchain-deskcryptohelps.com
View sourcePage captured
View sourcePD-20260913-1E9075 Recipient: abuse@ownregistrar.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
onchain-deskcryptohelps.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.