Skip to security report
coinexse.co favicon
Domain security and threat intelligence

coinexse.co

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

The coinexse.co domain displays a minimalist loading page that prompts visitors to connect a Web3 wallet via backend scripts. If you interacted with this site, immediately revoke any token approvals granted through your wallet.

Page title: “Buy Bitcoin”

More about the sources
Recorded security signals

Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

Stored blocklist matches: 2
Registrar
SwedenNAMEMART
Resolved IP
Canada104.21.49.96Cloudflare, Inc. · CDN
Registered
2026-09-14
First seen by PhishDestroy
2026-11-20
URLQuery
detections
Page captures
open gallery
Reports sent
view timeline
2026-11-20 1 Report Sent CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@namemart.com. The latest stored availability evidence still shows the domain reachable; 26 hours has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
26 hours
Reports sent
1
Latest case ID
PD-CB1123DDF90D57D589BC
Current status
HTTP 200 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded coinexse.co on 2026-11-20. Listed by external blocklists: MetaMask, SEAL. Risk: high (evidence score 66/100). Registrar: NAMEMART. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

High
Status
Last known active
Blocklist matches
2 external + PhishDestroy list
Hosting
Canada104.21.49.96Cloudflare, Inc. · CDN
Registrar
SwedenNAMEMART
Registered
2026-09-14
Page captures
6

URLScan capture · 2026-11-20 20:27 UTC · SHA-256 9779744e…95aec59

PhishDestroy analysis, reviewed version

Page layout and loading behavior

The coinexse.co page displays a minimal interface featuring a central logo mark and the text "loading...". The visual presentation relies on a clean, light background with a simple typographic spinner. Behind this loading state, the underlying scripts attempt to initiate a Web3 connection prompt using wagmi libraries. Visitors arriving at the URL are met with this waiting state rather than a fully rendered exchange interface. The address structure mimics prominent exchange naming patterns without officially representing them.

Wallet connection risks and security telemetry

Connecting a cryptocurrency wallet to an unverified interface can grant malicious smart contracts permission to drain funds. Because MetaMask and SEAL block it, the site is flagged by multiple security vendors. Furthermore, it sits behind Cloudflare, which hides the real server, while 14 Sep 2026 marks the domain creation date through NAMEMART PTE. LTD. The domain was still reachable on 20 Nov 2026 at 21:27 UTC. Because the page leverages automated connection libraries, visitors risk exposing their token balances to unauthorized third parties.

Recommended actions for visitors

Anyone who visited coinexse.co and attempted to connect a wallet should check their account permissions immediately. Use tools like Revoke.cash to disconnect any active allowances granted to unfamiliar contracts. Never sign unexpected transaction requests on unfamiliar web domains. Report the domain to your wallet provider to help protect other users from potential asset loss.

Source evidence 5 sources

URLScan

Page capture

SHA-256 4932c763…33ab5ef

Open report
URLScanOriginal source recordObserved: 20 fields
Separate monitor record · 2026-11-21 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1faa4-2598-71b8-8686-2d526ebc87ec
Score
0
Malicious
✗
Result at
2026-11-21T04:30:18Z
Enriched at
2026-11-21T09:11:12Z
Source timestamps
Urlscan result at: 2026-11-21 05:30:18; Urlscan enriched at: 2026-11-21 10:11:12

PhishDestroy DOM

15 / 100 · heuristic score · 0 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 15 / 100 · 2026-11-20 23:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
15
Analyzed at
2026-11-20T23:20:14Z
Source timestamp
2026-11-21 00:20:14
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
coinexse.co — Web3 wallet connection script analysis
AI description
coinexse.co shows a minimalist loading page designed to trigger Web3 wallet connections. MetaMask and SEAL block it. Revoke any token approvals.
AI summary
Page layout and loading behavior The coinexse.co page displays a minimal interface featuring a central logo mark and the text "loading...". The visual presentation relies on a clean, light background with a simple typographic spinner. Behind this loading state, the underlying scripts attempt to initiate a Web3 connection prompt using wagmi libraries. Visitors arriving at the URL are met with this waiting state rather than a fully rendered exchange interface. The address structure mimics prominent exchange naming patterns without officially representing them. Wallet connection risks and security telemetry Connecting a cryptocurrency wallet to an unverified interface can grant malicious smart contracts permission to drain funds. Because MetaMask and SEAL block it, the site is flagged by multiple security vendors. Furthermore, it sits behind Cloudflare, which hides the real server, while 14 Sep 2026 marks the domain creation date through NAMEMART PTE. LTD. The domain was still reachable on 20 Nov 2026 at 21:27 UTC. Because the page leverages automated connection libraries, visitors risk exposing their token balances to unauthorized third parties. Recommended actions for visitors Anyone who visited coinexse.co and attempted to connect a wallet should check their account permissions immediately. Use tools like Revoke.cash to disconnect any active allowances granted to unfamiliar contracts. Never sign unexpected transaction requests on unfamiliar web domains. Report the domain to your wallet provider to help protect other users from potential asset loss.
AI generated by
threat-v10-gemini
AI generated at
2026-11-20T23:32:19Z
Revision
018aea1c9858254dfe54a9f2934109725d0ce86ff33ed22eb486dbc52aa95bbd
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
VirusTotalOriginal source recordObserved: 12 fields
Open complete records
Website checksOriginal source recordRetrieved: 22 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.01
Average page size, bytes
2460

Trackers

Requests
3

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
144
Download
1
Response time, ms
211

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
3859
CO₂, grams
0.0001
Cleaner than, %
92

DNS servers

Nameservers
  • IP address
    108.162.193.62
    Host
    amir.ns.cloudflare.com
  • IP address
    172.64.34.195
    Host
    cora.ns.cloudflare.com
DNS zone
coinexse.co

Location

IP address
2606:4700:3032::ac43:bdbc
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Subject alternative names
  • coinexse.co
  • *.coinexse.co
Key size, bits
256
Certificate chain
  • coinexse.co
  • WE1
  • GTS Root R4
Issuer
Google Trust Services / WE1
Serial
3A80EB8DF78DC4960E14D19D3B660E36
SHA-256
e5c80103ba755973fde8c73e658c8c23962c485cf9292f1bead9979b94d3a5d7
Subject
coinexse.co
Valid until
Valid from

DNS records

A
  • 104.21.49.96
  • 172.67.189.188
NS
  • amir.ns.cloudflare.com
  • cora.ns.cloudflare.com
SOA
Primary nameserver
amir.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2420622589
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3032::ac43:bdbc
  • 2606:4700:3037::6815:3160

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3032::ac43:bdbc
IP version
6

Redirects

Redirect chain
  • https://coinexse.co

Subdomains

Count
1
Subdomains
  • www.coinexse.co

Registration record

Registrar
NAMEMART PTE. LTD.
Registrar IANA ID
4162
Registrar URL
http://www.namemart.com
Registered
Updated
Expires
Status
  • ok https://icann.org/epp
Nameservers
  • amir.ns.cloudflare.com
  • cora.ns.cloudflare.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=UTF-8
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-11-20T20:31:56Z; First: 2026-09-14T05:16:40Z; Changes: 1; Days archived: 2; Scans per day: 0.01; Avg page bytes: 2460
Trackers
Requests: 3
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 144; Download: 1; Response ms: 211
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 3859; Co2 grams: 0.0001; Cleaner than: 92
DNS server
NS: (IP: 108.162.193.62; Host: amir.ns.cloudflare.com), (IP: 172.64.34.195; Host: cora.ns.cloudflare.com); Zone: coinexse.co
Location
IP: 2606:4700:3032::ac43:bdbc; ASN: 13335; Org: Cloudflare, Inc.; City: Toronto; Country: CA
SSL
San: coinexse.co, *.coinexse.co; Bits: 256; Chain: coinexse.co, WE1, GTS Root R4; Issuer: Google Trust Services / WE1; Serial: 3A80EB8DF78DC4960E14D19D3B660E36; SHA256: e5c80103ba755973fde8c73e658c8c23962c485cf9292f1bead9979b94d3a5d7; Subject: coinexse.co; Valid to: 2027-02-10T02:59:56Z; Valid from: 2026-11-12T02:02:35Z
DNS records
A: 104.21.49.96, 172.67.189.188; NS: amir.ns.cloudflare.com, cora.ns.cloudflare.com; Soa: Nsname: amir.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2420622589; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:3032::ac43:bdbc, 2606:4700:3037::6815:3160
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2606:4700:3032::ac43:bdbc; Family: 6
Redirects
Chain: https://coinexse.co
Subdomains
Count: 1; Subdomains: www.coinexse.co
Registration record
Registrar: NAMEMART PTE. LTD.; Registrar iana ID: 4162; Registrar URL: http://www.namemart.com; Created: 2026-09-14T01:46:00Z; Updated: 2026-09-19T01:47:03Z; Expires: 2027-09-14T23:59:59Z; Status: ok https://icann.org/epp; Nameservers: amir.ns.cloudflare.com, cora.ns.cloudflare.com; Dnssec: unsigned
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=UTF-8

Questions about coinexse.co

Is coinexse.co safe to use?

No, because MetaMask and SEAL block it and security tools flag the domain as a risk. You should avoid interacting with any prompts on coinexse.co.

What happens if I connected my wallet to coinexse.co?

Connecting your wallet can expose your token balances to automated scripts or malicious approvals. You should check your wallet dashboard immediately and revoke any unknown permissions.

How can I revoke malicious approvals?

Use a trusted token allowance checker such as Revoke.cash to review all connected smart contracts. Disconnect and revoke permissions for any contract you do not recognize or trust.

Explore

Blocklist matches2 external + PhishDestroy list · MetaMask · PhishDestroy · SEAL 2
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Page captures (6)

All capture links and hashes (6)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 97 report ↗
IP Context Canada104.21.49.96 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar NAMEMART SE(SE)
Abuse contactabuse@namemart.com
RegistrationCreated 2026-09-14 (69d · New) — Expires 2027-09-14
Registrantf651612a2f356ad3s@ VirusTotal WHOIS
WHOIS statusNo restrictions
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-20
DOM Analysisanalyzed 2026-11-21score 15/100
Submitted URLhttp://coinexse.co/
Case ID
Observed page title
Buy Bitcoin
TLS Certificate
Issued by WE1 · stored validity ends in 79 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada104.21.49.96
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • amir.ns.cloudflare.com
  • cora.ns.cloudflare.com

SOA

  • nsname: amir.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2420622589
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-11-12 02:02:35
Valid until
2027-02-10 02:59:56
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte5c80103ba755973fde8c73e658c8c23962c485cf9292f1bead9979b94d3a5d7
Certificate names · 2 SANs
  • coinexse.co
  • *.coinexse.co

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-11-21 12:16 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-21 12:16 UTC
RDAP registration
Observed timeline last reachable: 2026-11-21 12:16 UTC last content: 2026-11-21 12:16 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.coinexse.coDomain record
Technologies · 6 identified
Open complete records

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://coinexse.co/
Final URL: https://coinexse.co/
Response
HTTP 200
HTML body
4.1 KB
Compressed
1.6 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
CF-Cache-Status: DYNAMIC
Server: cloudflare
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 12
Alt-Svc
h3=":443"; ma=86400
CF-Cache-Status
DYNAMIC
CF-Ray
a5da3303f8d1207f-TXL
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Fri, 20 Nov 2026 20:28:08 GMT
Last-Modified
Wed, 21 Oct 2026 07:12:47 GMT
Server
cloudflare
Server-Timing
cfEdge;dur=15,cfOrigin;dur=0,cfWorker;dur=353
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data107
Open complete records

Captured network requests

Network requests: 122 SHA-256 hashes: 122 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-21 09:20 UTC.

Open this scan on URLScan 01a1fd4c-417f-7536-9b6f-4fa488527d42 ↗

Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Serving page content

    page content returned

  2. Availability monitor · Recorded state

    Serving page content

    page content returned

  3. Domain monitor · First collection record

    Reachable

All retained availability observations5
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    coinexse.co detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Blocklist Detection · Automated brand label: Bitcoin · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: NAMEMART PTE. LTD.. Abuse contacts: 1.
    • abuse@namemart.com
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+67 d 18 h
  3. First abuse report sent+12 h 24 min

Reported 68 d 7 h after registration

  1. Abuse report sent

    PD-CB1123DDF90D57D589BC · Receipt 85482

    abuse@namemart.com
    +1 min
  2. URLScan

    Page captured

    +12 h 18 min
  3. Wayback Machine

    Page archived

    +3 min
  4. Added to PhishDestroy

    coinexse.co

How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

coinexse.co

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-CB1123DDF90D57D589BC Recipient: abuse@namemart.com
Page title stored with report: Buy Bitcoin & Crypto | Crypto Exchange, App & Wallet
PDF notice generated
Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including coinexse.co)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/coinexse.co"
  title="PhishDestroy threat report for coinexse.co"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>