How we checked this
We reviewed the linked sources and keep this page updated when the record changes. Use the source list below to verify the details.
Run a warning check
The page first checks wording in your browser, then asks the CryptoRescue warning index for cached matches. The server stores only a hash and result counts for diagnostics, not your pasted text.
Cached warning-index result
Recommended next steps
Search these exact strings
Generated source searches
Risk flags found in your text
Indexed source coverage
The checker does not confirm whether a regulator has listed the service. It builds the searches and flags risky wording so you can verify exact matches on official sources.
What this page helps you decide
- Should I send more money? If a warning or clone match appears, stop before paying any tax, validator, unlock or recovery fee.
- Is this the real company? Compare the exact domain, app name, email and support channel against warning-list clone language.
- What evidence should I save? Keep the warning URL, website URL, transaction hashes, wallet addresses, emails, chats and screenshots.
- Where should I report it? Use the official regulator or law-enforcement links below, then add exchange or wallet-provider reports when relevant.
Copy this before you search
| Item | Examples to copy |
|---|---|
| Domain | cryptosite-example.com, app subdomain, login URL, support URL |
| Brand and company name | Service name, legal entity, spelling variants, translated name |
| People and contacts | Telegram handle, WhatsApp number, email, social profile, support agent name |
| Payment trail | Wallet address, transaction hash, exchange receipt, payment request text |
| Offer wording | Guaranteed return, withdrawal tax, validator fee, recovery payment, liquidity unlock |
Five-minute check
- Copy the exact domain. Check the host in the address bar, not the logo on the page.
- Search the brand and company name. Try spelling variants, app names, support handles and the domain without https.
- Search warning lists before paying. Start with FCA, CFTC, SEC/Investor.gov and DFPI for crypto complaints.
- Compare the behavior. Seed phrase requests, unlock taxes, guaranteed recovery and remote access are red flags even if no warning appears.
- Save evidence before confronting anyone. Keep URLs, screenshots, wallet addresses, transaction hashes, emails and chat IDs.
Where to search
| Source | Search for | Best use | Link |
|---|---|---|---|
| FCA Warning List | Service name, domain, phone, email, clone brand | Useful for unauthorized firms, clone firms and fake investment/recovery offers. | open |
| CFTC RED List | Company name, trading platform, broker name | Useful when a platform claims trading, forex, derivatives, commodities or digital-asset investment services for US users. | open |
| SEC Investor Alerts | Offer name, token, promoter, investment pitch | Useful for crypto asset securities scam patterns and investor alerts. | open |
| CFTC Digital Asset Frauds | Recovery-fee pattern, fake exchange, guaranteed crypto returns | Useful for checking whether the behavior matches known digital-asset fraud patterns. | open |
| DFPI Crypto Scam Tracker | Domain, app, person name, scam type | Useful for complaint-based crypto scam patterns and clone/fake platform research. | open |
| FTC crypto scam guidance | Romance pitch, investment promise, recovery fee, payment demand | Useful for consumer red flags and next steps when someone asks for crypto payment. | open |
| OFAC Sanctions List Search | Entity name, alias, wallet-related service, sanctioned organization | Useful when a story or service claim mentions sanctions, mixers, blocked entities or restricted jurisdictions. | open |
| FBI IC3 | Report portal and annual trend reports | Use after an incident to report cyber-enabled fraud and preserve an official record. | open |
How to interpret a match
| Result | What to do |
|---|---|
| Exact match on regulator list | Stop sending funds. Save the warning URL and all evidence. Treat the service as high risk. |
| Similar name or clone warning | Check domain spelling, company registration claims and support channels. Do not rely on logo or chat messages. |
| No match found | Not a safety approval. Continue checking official domains, status pages, wallet prompts, fees and user reports. |
| Only social complaints found | Treat as a signal. Look for stronger sources before making public accusations or additional payments. |
| Recovery agent asks for fee or seed phrase | Stop. This is a high-risk pattern even if the name is not on a warning list yet. |
What to open next
| What you have | Best next step | Open |
|---|---|---|
| Suspicious domain or brand | Run the checker, then compare the exact spelling against clone-domain and service-profile pages. | open |
| Known exchange name | Open the exchange status monitor and the relevant service profile before trusting a support message. | open |
| Wallet address or transaction hash | Use the transaction lookup router and save explorer URLs before reporting. | open |
| Recovery offer after a loss | Read the recovery-scam explainer and avoid advance fees, seed phrases and remote access. | open |
| Evidence already exists | Build a clean incident file before chats, domains or public pages disappear. | open |
If you already sent money
- Do not pay a second fee, tax, validator charge, recovery deposit or unlock payment.
- Write a timeline: first contact, website, deposit, withdrawal block, support messages and every payment request.
- Save transaction hashes, wallet addresses, exchange receipts, emails, screenshots and profile URLs.
- If a wallet seed phrase or private key was exposed, treat the wallet as compromised and protect remaining assets from a clean device.
- Report through official channels such as IC3, relevant regulators, exchanges and abuse-reporting platforms.
Important limit
No warning list is complete or real-time. A new scam, clone domain or fake recovery service may not appear in official lists yet. Treat this page as one safety check, not as a final approval system.
Update log
- 3 Jun 2026Published with source tracking and reader-safety context.
- CorrectionsIf a source changes or a claim needs clarification, this page can be updated from the editorial desk.