VirusTotal
8 / 91 engine detections
レポートを開く“Limitless Exchange”
暗号資産フィッシング: liimtless.exchange — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 8/91 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
8 / 91 engine detections
レポートを開く悪意あり
レポートを開く24 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
The domain liimtless.exchange is a generic phishing site posing as a fake cryptocurrency exchange. It does not impersonate a known brand but operates as a standalone scam designed to steal user credentials or funds. As of the latest verification, liimtless.exchange has been taken offline, though it previously exhibited elevated risk indicators associated with fraudulent activity.
Technical analysis of liimtless.exchange reveals limited but notable detection. The domain was flagged by 2 of 95 security vendors on VirusTotal, including Fortinet and SOCRadar. It appears on 3 security blocklists, specifically PhishDestroy, MetaMask, and SEAL. Registered through NiceNIC International Group Co., Limited on February 21, 2026, the domain resolves to the IP address 172.67.209.67, hosted on Cloudflare’s infrastructure (AS13335) in the US. The SSL certificate is issued by Google Trust Services / WE1, and the observed page title was 'Just a moment...' with an HTTP 500 status. Nameservers are jack.ns.cloudflare.com and etta.ns.cloudflare.com, and the site uses Cloudflare and HTTP/3 technologies.
Users who interacted with liimtless.exchange should immediately change any credentials entered on the site and enable two-factor authentication on affected accounts. Monitor financial accounts and transaction histories for unauthorized activity. If cryptocurrency was involved, revoke any token approvals granted to the domain and consider transferring funds to a new wallet. Report the phishing domain to local cybersecurity authorities, the registrar (NiceNIC), and platforms like Google Safe Browsing or PhishTank to aid in broader mitigation efforts.
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 の評判はこのドメインに起因しません。
etta.ns.cloudflare.comLocation describes the IP network.
26e3f0c064568627ce090800c46c24c59bf80ef06de039f0ac89b23a23d3a10dSaved 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 liimtless.exchange · checked Apr 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.
cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
liimtless.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
利用不可→到達可能
https://radar.cloudflare.com/scan/560d3c26-13d9-4045-aa8a-424ff0c1ce9b
到達可能→利用不可
No threat flag
View source24 community references
View source8/91 engine detections
View sourcePage captured
View sourceliimtless.exchange
View sourceコミュニティの 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 ↗
liimtless.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.