This domain, polymarkets.reserved.market, is identified as a brand impersonation threat targeting Polymarket, a reputable platform for private markets. The domain was created on October 23, 2025, and has been taken offline as of the latest check. It poses a significant risk to users who may mistake it for the legitimate Polymarket website, potentially leading to exposure of sensitive information and financial loss.
Analysis indicates that polymarkets.reserved.market has been flagged by 11 out of 95 security vendors on VirusTotal, suggesting a moderate level of detection and concern among the security community. The domain uses an SSL certificate issued by Google Trust Services, which can lend a false sense of security to unsuspecting users. The domain is registered through Cloudflare, Inc., and was previously resolving to the IP address 172.67.187.195, located in the United States under the AS13335 Cloudflare, Inc. network. It appears on one security blocklist, specifically PhishDestroy, further indicating its malicious intent.
If users have visited polymarkets.reserved.market, they should immediately check their Polymarket account for any unauthorized activity. It is recommended to change any passwords used on the legitimate Polymarket site and enable multi-factor authentication (MFA) as an additional layer of security. Users should also monitor their financial statements for any unusual transactions and report any suspicious activity to Polymarket's support team. To avoid similar threats in the future, users should verify the URL of the website they are visiting and only access the official site through trusted bookmarks or links.
DOM Analysisanalyzed 2026年7月28日score 88/1001 brand signal
Submitted URLhttp://polymarkets.reserved.market/
Favicon Hash
ICANN OVERSIGHTRegistration: reserved.market
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For the registrable domain reserved.market behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
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.
Certificate fingerprintcaa9eba9398b77f65af5134c20dca334d42084305065b8b1f1379f321c856c8aCertificate names · 1 SANs
reserved.market
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 22:06:44 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:06:44 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.
技术 · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Performance monitoring tool that measures website speed from real users.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
16 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
(US)
