Skip to security report
polymarkex.com favicon
Domain security and threat intelligence

polymarkex.com

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

polymarkex.com: VirusTotal 0/92 detections. First recorded 2026-11-22. Registrar: Realtime Register B.V.

Page title: “Polymarkex | Prediction Markets”

More about the sources

Use caution — do not enter credentials or personal information.

Stored PhishDestroy threat listing Young domain: 29 days old
Registrar
Realtime
Resolved IP
45.202.214.243
Registered
2026-10-24
First seen by PhishDestroy
2026-11-22
Page captures
open gallery
2026-11-22

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

High
Hosting
45.202.214.243
Registrar
Realtime
Registered
2026-10-24
Page captures
3

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.

Source evidence 2 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
VirusTotalOriginal source recordObserved: 13 fields
Open complete records

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (3)

All capture links and hashes (3)

Domain details

Domain
Registrar Realtime
RegistrationCreated 2026-10-24 (29d · Very New!) — Expires 2027-10-24
Technical detailsProvenance & timestamps
First Detected2026-11-22
Submitted URLhttp://polymarkex.com/
Favicon Hash
Observed page title
Polymarkex | Prediction Markets
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 68 days

Network & certificates

Stored technical evidence

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-11-01 02:15:57
Valid until
2027-01-30 02:15:56
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint6cb594300a8b02774c18d6471e5787fad349e5e82fc0add88bb06a60f4055b74
Certificate names · 1 SAN
  • polymarkex.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://polymarkex.com/
Final URL: https://polymarkex.com/
Polymarkex | Prediction Markets
Explore prediction markets, event probabilities, sports, crypto and perpetual contracts on Polymarkex.
Response
HTTP 200
HTML body
5.9 KB
Compressed
1.7 KB
Links
1 internal · 0 external
Selected response headers
Server: Xcdn
Content-Type: text/html; charset=utf-8
Cache-Control: no-store, no-transform
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: Polymarkex | Prediction Markets
Open Graph description: Explore prediction markets, event probabilities, sports, crypto and perpetual contracts on Polymarkex.
Twitter card: summary_large_image
Saved response-header values · 10
Cache-Control
no-store, no-transform
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sun, 22 Nov 2026 18:16:01 GMT
Etag
W/"1783-G4VB+6kUNecJldUfdX/LPprtFy8"
Server
Xcdn
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Request-ID
01a20478-e33d-72d2-9011-9db1da30c1f1

Values retained by the collector; long values may be shortened during collection.

Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data66
Open complete records

Captured network requests

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 ↗

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Domain monitor · First collection record

    Reachable

All retained availability observations0

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.

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    polymarkex.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Automated brand label: Polymarket · Forensic Evidence Collected recorded
Publication & AvailabilityDestroyList Published recorded

Recorded activity

3 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+29 d 8 h
  1. Wayback Machine

    Page archived

    +1 min
  2. Added to PhishDestroy

    polymarkex.com

    same minute
  3. URLScan

    Page captured

How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

All stored records by source

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

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

polymarkex.com

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including polymarkex.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/polymarkex.com"
  title="PhishDestroy threat report for polymarkex.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>