VirusTotal
15 / 91 engine detections
レポートを開く“ExLimit — Обмен USDT на Наличные | Криптообменник”
Coingeckoなりすまし: exlimit.exchange — クローク済み · 到達可能 (HTTP 308). 証拠の概要: VirusTotal 15/91 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, Chong Lua Dao, ESET)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 91 engine detections
レポートを開くchecked — no detections recorded
レポートを開くchecked — no match recorded
23 community references
レポートを開く12 確認済み — ブロックなし
Scan report
レポートを開く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
PhishDestroy identifies exlimit.exchange as an active crypto credential-stealing site running since January 29, 2026. The domain advertises itself as a new exchange, but its real purpose is to trick visitors into connecting crypto wallets and signing malicious transactions that drain funds. Independent testing shows only 2 out of 95 VirusTotal security engines currently detect the threat, leaving most antivirus tools blind to the danger. WHOIS records reveal the domain was registered through Name.com, Inc. and resolves to the IP address 216.150.16.65. A Let’s Encrypt SSL certificate gives the site a deceptively trustworthy appearance, but SSL alone does not guarantee safety. If you visited exlimit.exchange or entered any wallet credentials, immediately disconnect any crypto wallets, revoke any signed permissions through your wallet’s “Connected Apps” or “Authorization” menu, and move remaining assets to a clean wallet on a different device. Scan your computer with updated antivirus software and consider rotating all passwords used on suspicious sites. Block the domain at your network level and report the URL to your local cybercrime unit to help protect others.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/+T64Gldfw2EM0MzdiStored page referencehttps://t.me/ex_limitStored page referenceIoC extraction recorded 2026-07-29 02:06:44 UTC
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 の評判はこのドメインに起因しません。
ns1.vercel-dns.comns2.vercel-dns.comLocation describes the IP network.
880fca51ff02975f41bd28fa00fd44155fc7b003a4595e459d4247272398849fSaved 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 exlimit.exchange · checked Apr 10, 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.
status_split · redirect: raw=redirect_308; http=308; via=http_proxy; location=https://exlimit.exchange/; server=Vercel
exlimit.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
protected→redirected
http_redirect
redirected→protected
http_access_restricted · access_restriction
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
No threat flag
View source23 community references
View source15/91 engine detections
View sourceexlimit.exchange
View sourceコミュニティの 1 人が報告・初回確認 2026年4月10日
Listed 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 ↗
exlimit.exchange)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.