The domain polymarketprivate.reserved.market was observed hosting a brand‑impersonation page titled "Polymarket - Private Markets" and is currently listed as offline. Infrastructure analysis shows the domain resolves to IP address 104.21.68.61, which belongs to Cloudflare, Inc. (ASN 13335) and is geolocated in the United States. Registration records indicate the domain was registered through Cloudflare, Inc., and the TLS certificate presented is issued by Google Trust Services under the WE1 certificate authority, confirming a legitimate‑looking HTTPS configuration.
The site served HTTP/3 and returned a 404 status code at the time of scanning, suggesting the malicious landing page may have been removed or temporarily unavailable. Detection metrics reveal that 13 of 95 security vendors on VirusTotal flagged the domain, and it is present on a single security blocklist. The domain has been actively blocked by the PhishDestroy mitigation service.
While the available evidence confirms the presence of brand‑impersonation activity targeting Polymarket, no additional artifacts such as login forms or credential‑stealing scripts have been disclosed. Defenders should continue to monitor the domain’s DNS and IP reputation, ensure that any outbound connections to 104.21.68.61 are logged, and enforce blocklist rules that include this domain. Given the SSL certificate’s legitimacy and the use of Cloudflare’s infrastructure, threat actors may rely on reputable services to increase credibility, so organizations should treat similar Cloudflare‑hosted domains with heightened scrutiny even when the content appears to be absent.
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:41 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:06:41 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.
技术 · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
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.
17 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)
