VirusTotal
13 / 91 engine detections
レポートを開く“Limitless Exchange”
シードフレーズ・フィッシング: limitedless.exchange — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 13/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Forcepoint…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 91 engine detections
レポートを開く悪意あり
レポートを開く24 community references
レポートを開くprovider verdict: clean
レポートを開く14 確認済み — ブロックなし
No threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, limitedless.exchange, presents a high-risk brand impersonation threat specifically targeting users of the MetaMask cryptocurrency wallet service. Analysis indicates the site mimics legitimate MetaMask interfaces under the false pretense of a "Limitless Exchange," likely designed to harvest wallet credentials, recovery phrases, or other sensitive authentication details. The infrastructure appears engineered to deceive users into believing they are interacting with an official MetaMask platform, thereby facilitating unauthorized access to digital assets. Evidence supporting this assessment includes multiple technical indicators. The domain is flagged by 12 out of 95 security vendors on VirusTotal, and it appears on three distinct security blocklists. Registered through NiceNIC International Group Co., Limited on February 21, 2026, the domain resolves to the IP address 104.21.25.54 and is currently offline. The SSL certificate is issued by Google Trust Services, while technologies such as HSTS, Cloudflare, and HTTP/3 are detected, suggesting an attempt to appear legitimate and secure. Additionally, the domain holds a Gridinsoft trust score of 0/100, further confirming its malicious nature. Users who have visited limitedless.exchange should take immediate action to mitigate potential risks. If any credentials, recovery phrases, or personal information were entered on the site, affected accounts should be considered compromised. Users are advised to revoke any connected sessions, transfer assets to a new secure wallet, and monitor for unauthorized transactions. Enabling multi-factor authentication on all related accounts and reporting the incident to relevant security teams or financial institutions is strongly recommended. Vigilance against similar threats should be maintained, particularly when interacting with cryptocurrency-related platforms.
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 の評判はこのドメインに起因しません。
piotr.ns.cloudflare.comLocation describes the IP network.
3ad3acc07b7ea4c7ae066ad1460f903c9f980f035a4a2d722ac365817f8ef136Saved 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 limitedless.exchange · checked Jun 27, 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_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
limitedless.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
protected
cloudflare_challenge · Cloudflare · challenge
利用不可→到達可能
2→12
到達可能→利用不可
13/91 engine detections
View source24 community references
View sourceNo threat flag
View sourcelimitedless.exchange
View source保存された類似ドメイン:79 件
コミュニティの 1 人が報告・初回確認 2026年2月12日
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 ↗
limitedless.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.