VirusTotal
6 / 89 engine detections
打开报告钓鱼: cow.limited — 内容不可用. 证据摘要: VirusTotal 6/89 (ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft); PhishDestroy score 73/100. 注册商…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 89 engine detections
打开报告5 community references
打开报告provider verdict: clean
打开报告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
cow.limited was an impersonation phishing page built to pass as a genuine crypto service and capture whatever visitors trusted it with. PhishDestroy first detected it on 2026-09-13. Within a week it went offline: the site has been dead since 2026-09-20, and its DNS was still inactive when last checked on 2026-10-19. The short, brand-like name on a .limited extension is typical of lookalike domains meant to look official in a link or search result.
Impersonation pages copy the look, wording and flow of a real platform so the visitor believes they are on the official site. From there the page asks for something valuable. That might be a wallet connection and transaction signature, a recovery phrase presented as a "verification" step, or account credentials typed into a cloned login form. Whatever is entered goes straight to the operators. For a crypto user, that can mean an emptied wallet or a hijacked exchange account, and on-chain transfers cannot be reversed.
Six of 89 VirusTotal engines flagged the domain as of 2026-09-21: ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. The detection count is modest. Still, ChainPatrol focuses on Web3 brand protection, and its flag points to a page aimed at crypto users. The domain also appears in five AlienVault OTX threat pulses, which shows other researchers tracked it independently. It is listed on the PhishDestroy blocklist.
The domain was registered on 2025-08-14 through Tucows Domains Inc., roughly thirteen months before it surfaced as phishing. Holding a domain that long before using it is a common way to avoid filters that distrust brand-new registrations. It resolved to Amazon (AMAZON-02) cloud hosting in the United States. Its TLS certificate came from GoDaddy's domain-validated CA, so the padlock only proved control of the domain and never confirmed who ran the site.
If you connected a wallet to cow.limited, open a token-approval manager and revoke any permissions granted around that time. If you typed in a recovery phrase, treat the wallet as compromised and move your funds to a new wallet with a fresh seed. If you entered a password, change it everywhere you reused it and enable app-based or hardware 2FA. Always reach crypto services through bookmarks or official app listings rather than links. Defenders should block the domain and look for the same lookalike pattern on other extensions.
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.
ns2.renewyourname.netLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
4→6
可访问→不可用
可访问
5 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcecow.limited
View source1 条社区报告
类别PHISHING
Dear Team, We are writing to report a domain that holds a place in search results under the name of the CoW Swap exchange and collects the people who go looking for that service. A query in Bing returns cow[.]limited at the head of the results, titled "CoW Swap — Instant Crypto
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cow.limited
“Dear Team, We are writing to report a domain that holds a place in search results under the name of the CoW Swap exchange and collects the people who go looking for that service. A query in Bing returns cow[.]limited at the head of the results, titled "CoW Swap — Instant Crypto Swaps, Low Fees", described as "MEV-protected token swaps across 11 chains" with the invitation to "Trade smarter and keep more of every swap", and illustrated with a card drawn in the exchange's house colours. A search”
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 ↗
cow.limited)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.