Cloudflare Radar
Suspicious
レポートを開く“ZapTRX — Swap USDT to TRX with Zero Gas”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 39 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.
Bitgetなりすまし: zaptrx.cfd — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 0/92; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 66/100. レジストラ…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
Suspicious
レポートを開く0 / 92 engine detections
レポートを開くScan report
レポートを開く2 community references
レポートを開く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
PhishDestroy classifies zaptrx.cfd as a crypto wallet drainer and first observed it on 2026-10-19. The page title captured on 2026-10-19 advertises “ZapTRX — Swap USDT to TRX with Zero Gas”. An HTTP check returned 403 on 2026-10-19, and the domain was marked offline that day; these entries do not establish who caused the change.
Wallet drainers generally seek signatures or token permissions that allow an attacker to transfer assets. This explains the risk category assigned by PhishDestroy; the captured title alone does not prove that this particular page executed such a transaction.
VirusTotal reported 0 of 92 engines flagging the domain in its 2026-10-15 analysis, retrieved on 2026-10-19. Google Safe Browsing and the matched urlscan capture did not flag it as malicious on 2026-10-19. MetaMask and SEAL appeared among the checked external blocklists that day, separately from PhishDestroy’s internal listing. OTX reported two pulses mentioning the domain.
The domain was registered on 2026-10-14 through Spaceship, Inc. The 2026-10-19 capture recorded IP 188.114.96.3 on Cloudflare’s network; this does not identify the origin server or the operator’s location.
If you granted token permissions through this page, review and revoke suspicious approvals using your wallet’s verified tools. If you disclosed a seed phrase or private key, use a new securely created wallet; approval revocation does not repair exposed keys. Defenders should investigate the exact hostname and relevant transactions, without blocking the entire shared hosting network.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
TNUC9Qb1rRpS5CbWLmNMxXBjyFoydXjWFRFormat validated · Domain analysisIoC extraction recorded 2026-10-19 04:00:07 UTC
Last checked
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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 の評判はこのドメインに起因しません。
keanu.ns.cloudflare.comziggy.ns.cloudflare.comLocation describes the IP network.
d88299fe324992d14b479d41d6b6e85f8726f90a9bc5c5df0d39751591245f4fSaved 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 zaptrx.cfd · checked Oct 19, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://zaptrx.cfd/https://zaptrx.cfd/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400defaultDYNAMICa4cc0c6d7fec3a44-FRAkeep-alivegzipframe-ancestors http: https:text/htmlMon, 19 Oct 2026 01:35:52 GMTSun, 27 Sep 2026 01:59:00 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=EMSVGk3poJw995ONC2NEAWSK3ojPThZn5eaatXfwsd5Hq4LKvdti6T62n%2FWqCuDssyr2TqAkCZSIdPB0QQDKqGWW7u9LhJQkDuG3Hf1cqjE%2FtTM61wWWzb9kHssF"}]}cloudflaremax-age=63072000; includeSubDomains; preloadchunkedaccept-encodingnosniff1; mode=blockValues 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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_direct; server=cloudflare; provider_error=cloudflare_phishing_interstitial
zaptrx.cfd
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
PD-20261019-EC6294
2 community references
View sourceNo threat flag
View source0/92 engine detections
View sourcePage captured
View sourcezaptrx.cfd
View sourcePD-20261019-EC6294 Recipient: abuse@spaceship.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
zaptrx.cfd)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.