Cloudflare Radar
Scan report
Open reportpolymarkex.com: VirusTotal 0/92 detections. First recorded 2026-11-22. Registrar: Realtime Register B.V.
Page title: “Polymarkex | Prediction Markets”
Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Recorded source summary
PhishDestroy first observed polymarkex.com on Nov 22, 2026. Stored content metadata identifies Polymarket as the apparent target. The captured page title is “Polymarkex | Prediction Markets”. Current evidence score: 45/100 (high).
VirusTotal recorded 0 detections among 92 engines on Nov 17, 2026 at 22:53 UTC.
The collector marked the hostname reachable on Nov 22, 2026 at 18:14 UTC, but did not retain the HTTP response code. Registration records for the domain list Realtime Register B.V. as the registrar and Oct 24, 2026 as the creation date. Registration preceded first observation by 29 days. At collection time, the hostname resolved to 45.202.214.243. The stored server header is Xcdn. The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and Cloudflare Radar. TLS metadata lists Let's Encrypt / YE2 as the certificate issuer with validity through Jan 30, 2027.
The classification is based on stored page-analysis fields. The target field identifies Polymarket.
Scan report
Open reportPage capture
SHA-256 5efa0498…d013e27
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
georgia.ns.cloudflare.comwatson.ns.cloudflare.com6cb594300a8b02774c18d6471e5787fad349e5e82fc0add88bb06a60f4055b74polymarkex.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://polymarkex.com/https://polymarkex.com/Server: XcdnContent-Type: text/html; charset=utf-8Cache-Control: no-store, no-transformContent-Encoding: gzipsummary_large_imageno-store, no-transformkeep-alivegziptext/html; charset=utf-8Sun, 22 Nov 2026 18:16:01 GMTW/"1783-G4VB+6kUNecJldUfdX/LPprtFy8"XcdnchunkedAccept-Encoding01a20478-e33d-72d2-9011-9db1da30c1f1Values 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.
Network requests: 194 SHA-256 hashes: 191 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-22 18:16 UTC.
Open this scan on URLScan 01a20476-4d11-7651-be73-5e69e1fe6cbe ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
No retained observations are recorded.
Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
polymarkex.com Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose 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 ↗
polymarkex.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.
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.