VirusTotal
6 / 91 engine detections
打开报告“polymarket.charity is registered at Namecheap”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 3 months 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.
钓鱼: polymarket.charity — 最后已知的活跃状态 (HTTP 302). 证据摘要: VirusTotal 6/91 (alphaMountain.ai, Chong Lua Dao, CRDF, Forcepoint ThreatSeeker, Fortinet); URLQuery 2…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 91 engine detections
打开报告2 det.
打开报告3/14
DBL_PHISH
5 community references
打开报告provider verdict: clean
打开报告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
This domain is flagged as a cryptocurrency wallet phishing site under active investigation. Analysis indicates it poses a high-risk threat to users of decentralized finance platforms, specifically targeting wallet credentials and private keys through fraudulent interfaces mimicking legitimate services. The domain exhibits characteristics of a credential harvesting operation, likely designed to exfiltrate sensitive financial data from unsuspecting victims. Infrastructure analysis reveals the following technical indicators: registered through NAMECHEAP INC on June 29, 2026, resolving to IP address 162.255.119.196. VirusTotal detection ratio stands at 0/95, suggesting the domain has not yet been widely flagged by security vendors. The domain was taken offline, but its recent creation date and lack of prior reputation indicate it was likely deployed for a short-term phishing campaign. No blocklist entries or trust scores were recorded at the time of assessment, further emphasizing its stealthy nature. Mitigation steps for this threat type include immediate blocking of the domain and associated IP address across all network security controls. Organizations should implement strict filtering rules for newly registered domains, particularly those using terms related to cryptocurrency or financial services. End users should be educated to verify domain authenticity through official sources and avoid entering wallet credentials on unfamiliar sites. Security teams are advised to monitor for connections to 162.255.119.196 and investigate any related network activity, as this may indicate compromise. Given the domain's recent creation and lack of detection, proactive hunting for similar infrastructure patterns is recommended.
Last checked
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.
dns1.registrar-servers.comdns2.registrar-servers.comeforward1.registrar-servers.compriority 10eforward3.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
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.
redirect: raw=redirect_302; http=302; via=http_proxy; location=http://www.polymarket.charity/; server=namecheap-nginx
polymarket.charity
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→redirected
http_redirect
未知→redirected
http_redirect
不可用→可访问
可访问→不可用
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
5 community references
View source6/91 engine detections
View sourcePage captured
View sourcePD-20260630-A2FC94
No threat flag
View sourcepolymarket.charity
View sourcePD-20260630-A2FC94 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
polymarket.charity)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.