VirusTotal
11 / 92 engine detections
打开报告“CoinP”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@godaddy.com.
The latest stored availability evidence still shows the domain reachable; 27 days 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.
钓鱼: coinpssj.com — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 11/92 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); URLQuery 3 det.; URLScan…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
11 / 92 engine detections
打开报告3 det.
打开报告Suspicious
打开报告恶意
打开报告6 community references
打开报告No threat flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
coinpssj.com is an impersonation phishing page that presents itself as "CoinP", a crypto-flavoured brand meant to look like a legitimate trading or wallet service. It targets cryptocurrency users who land on it from ads, messages or search results. PhishDestroy first flagged it on 2026-09-23. As of 2026-10-19 the site was still online and serving its content, so it remains a live risk.
Sites in this category copy the look and name of a real crypto platform, here under the page title "CoinP", so visitors trust it enough to act. The victim is typically asked to sign in, register, connect a wallet or make a deposit. Credentials typed into the page go straight to the operators, and deposited coins cannot be recovered. Any wallet connection or signature request is used to move funds out. Some of these sites also invent "fees" or "verification" payments before a withdrawal can go through.
11 of 92 engines on VirusTotal flagged the domain as of 2026-10-07. Those engines include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. urlscan.io returned a malicious verdict and tagged the page as a crypto scam. The domain is also listed on the MetaMask and SEAL blocklists alongside PhishDestroy. Six AlienVault OTX threat pulses reference it, so several research groups have tracked it independently.
The domain was registered through GoDaddy.com, LLC on 2026-09-08, just 15 days before PhishDestroy caught it. That short gap fits a site set up quickly for a campaign. Traffic runs through Cloudflare, Inc. with a Canada geolocation, which means the real origin server is hidden behind the proxy. The HTTPS certificate comes from Google Trust Services, so the padlock in the browser says nothing about whether the site is legitimate.
If you entered a password or email on coinpssj.com, change that password everywhere you reused it and turn on app-based 2FA. Do not send further "fees" or "verification" payments, as they only add to your losses. If you connected a wallet or signed anything, revoke the approvals it received with a token-approval checker. Move any remaining assets to a fresh wallet if you entered a seed phrase. Defenders should block the domain at DNS and proxy level and report it to Cloudflare and GoDaddy abuse.
Last checked
Edge-IP 声誉不属于此域。
kai.ns.cloudflare.comzainab.ns.cloudflare.comLocation describes the IP network.
22a3f7b7d151247c6d4b3ebbcad00ae54f21188424428d07b15c9311d4f59972Saved 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 coinpssj.com · checked Sep 23, 2026
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.
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
可访问
11/92 engine detections
View sourceNo threat flag
View source6 community references
View sourcePD-20260923-F2DBE4
Page captured
View sourcecoinpssj.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
coinpssj.com
PD-20260923-F2DBE4 Recipient: abuse@godaddy.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 ↗
coinpssj.com)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.