URLQuery
2 det.
Open reportThe 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”
Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
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.
URLScan capture · 2026-11-20 20:27 UTC · SHA-256 9779744e…95aec59
PhishDestroy analysis, reviewed version
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.
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.
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.
2 det.
Open reportScan report
Open reportPage capture
SHA-256 4932c763…33ab5ef
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
15 / 100 · heuristic score · 0 brand references · 0 classifications
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| 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 |
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.
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.
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.
Last checked
Edge-IP reputation is not attributed to this domain.
amir.ns.cloudflare.comcora.ns.cloudflare.comnsname: amir.ns.cloudflare.comhostmaster: dns.cloudflare.comserial: 2420622589refresh: 10000retry: 2400expire: 604800minttl: 1800Location describes the IP network.
e5c80103ba755973fde8c73e658c8c23962c485cf9292f1bead9979b94d3a5d7coinexse.co*.coinexse.coSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was serving its pages at the latest check.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.coinexse.coDomain recordTimestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://coinexse.co/https://coinexse.co/Content-Type: text/html; charset=UTF-8CF-Cache-Status: DYNAMICServer: cloudflareContent-Encoding: gziph3=":443"; ma=86400DYNAMICa5da3303f8d1207f-TXLkeep-alivegziptext/html; charset=UTF-8Fri, 20 Nov 2026 20:28:08 GMTWed, 21 Oct 2026 07:12:47 GMTcloudflarecfEdge;dur=15,cfOrigin;dur=0,cfWorker;dur=353chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Serving page content
page content returned
Serving page content
page content returned
Reachable
Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 68 d 7 h after registration
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
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| ID | Stored data |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
coinexse.co PD-CB1123DDF90D57D589BC Recipient: abuse@namemart.com 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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose 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 ↗
coinexse.co)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.