URLQuery
3 det.
Open reportPhishDestroy first recorded polexbot.pro on 2026-10-25. Listed by external blocklists: MetaMask, SEAL.
Page title: “Polexbot: Automated Polymarket Bot for 5-Minute Crypto Rounds”
Listed by external blocklists: MetaMask, SEAL. 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.
The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@identitydigital.com. The latest stored availability evidence still shows the domain reachable; 28 days 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.
PhishDestroy analysis, earlier unreviewed version
The captured screenshot from 2026-10-25 shows a dark gold landing page headed Automated Trading on 5 Minute Rounds, offering an AI bot for Polymarket's five-minute crypto rounds, with an Open Dashboard button, AI configuration chips and market cards with BUY YES prompts. Metadata described an automated Polymarket bot covering BTC, ETH, SOL, XRP, DOGE and BNB. PhishDestroy listed the page for impersonation because it trades on the Polymarket brand on a domain registered the day before. First seen by PhishDestroy on 2026-10-25.
The page routes visitors to a dashboard behind an automation pitch, a pattern in which a copycat collects account credentials or payment details from people who believe they are using the genuine Polymarket service. The lure is a bot claiming to place an up or down position each round inside visitor-set limits. Treat the offer as unverified impersonation rather than an authorized Polymarket tool.
The screenshot shows branded navigation, AI strategy chips and market cards borrowing Polymarket's name. urlscan's machine-learning engine scored the capture malicious at 97 on 2026-10-25 while its overall verdict stayed clean. VirusTotal did not flag the domain. Spamhaus listed it under the spam category on 2026-10-25; the MetaMask and SEAL blocklists plus PhishDestroy's internal list flagged it on 2026-10-26; OTX carried 4 pulses on 2026-10-25; Google Safe Browsing was not flagged on 2026-10-26. A same-domain redirect chain led to the captured page, whose scripts showed an Express on nginx stack with Google Tag Manager and Google Analytics, no React, Vue or Next globals, and a document hash starting 4f3ae770ccf7.
The domain was registered 2026-10-24 through NICENIC INTERNATIONAL GROUP CO., LIMITED and the capture was served from Amazon CloudFront behind nginx with Express headers; no firewall vendor was shown. Notable weaknesses: DNSSEC unsigned, no DKIM recorded, COOP, COEP and CORP absent, and one check reported no HSTS header. Otherwise TLS 1.3 with TLS-AES-128-GCM-SHA256, forward secrecy and ALPN h2; CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy present; SPF and DMARC present; CAA record present.
If you entered a password or payment details on polexbot.pro, change that password on the genuine Polymarket service and enable two-factor authentication. Defenders should block polexbot.pro at DNS, proxy and mail gateways and hunt for it in web logs and referral data. PhishDestroy's impersonation listing stands regardless of clean verdicts from other feeds.
3 det.
Open reportSuspicious
Open report1/100
Trust score, lower = worse
Open reportspam domain
4 community references
Open reportPage capture
Open reportSeparate stored monitor snapshot; does not replace the primary report record or establish current availability.
90 / 100 · heuristic score · 7 brand references · 1 classification
Content heuristic only; not the final score
Open reportNarrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
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.
| Mail configuration | Spf: v=spf1 -all; Dmarc: ✓; Spf lookups: 0 |
|---|---|
| Caa records | Domain: polexbot.pro |
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Crawler rules | Agents: *; Present: ✓; Sitemaps: https://www.polexbot.pro/sitemap.xml |
| Sitemap | Present: ✓; URL count: 31 |
| Security contact file | Present: ✓; Found in: /.well-known/security.txt |
| Page title and metadata | Ogurl: https://www.polexbot.pro/; Title: Polexbot: Automated Polymarket Bot for 5-Minute Crypto Rounds; Author: Polexbot; Ogtype: website; Robots: index,follow; Ogimage: https://www.polexbot.pro/og-image.jpg; Ogtitle: Polexbot: Automated Polymarket Bot for 5-Minute Crypto Rounds; Keywords: Polexbot, Polymarket bot, automated trading bot, 5 minute crypto rounds, prediction market bot, BTC ETH SOL XRP DOGE BNB, up or down bot; Ogsitename: Polexbot; Description: Polexbot automates Polymarket's 5-minute crypto up/down rounds. It covers BTC, ETH, SOL, XRP, DOGE and BNB, taking a position every round strictly within the limits you set.; Twittercard: Summary large image; Canonicalurl: https://www.polexbot.pro/; Ogdescription: Polexbot works Polymarket's 5 minute crypto rounds for you, taking an up or down position each round inside the limits you set. |
| Trackers | Requests: 22; Trackers: (Name: Google Tag; Company: Google; Country: US; Category: Advertising; Requests: 1), (Name: Amazon Web Services; Company: Amazon; Country: US; Category: Hosting; Requests: 2), (Name: Google Fonts; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: Google Static; Company: Google; Country: US; Category: Hosting; Requests: 3), (Name: Google Analytics; Company: Google; Country: US; Category: Site Analytics; Requests: 1) |
| Forms and mixed content | No sri: https://www.googletagmanager.com/gtag/js; Third party scripts: 1 |
| Status | Up: ✓; Code: 301; Timings: DNS: 29; TLS: 12; Wait: 15; Connect: 14; Download: 0; Response ms: 70 |
| TLS connection | Alpn: h2; Cipher: TLS_AES_128_GCM_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 80, 443 |
| Carbon | Bytes: 208908; Co2 grams: 0.0076; Cleaner than: 6 |
| DNS server | NS: (IP: 205.251.192.95; Host: ns-95.awsdns-11.com), (IP: 205.251.196.240; Host: ns-1264.awsdns-30.org), (IP: 205.251.199.244; Host: ns-2036.awsdns-62.co.uk), (IP: 205.251.194.210; Host: ns-722.awsdns-26.net); Zone: polexbot.pro |
| Cookies | Cookies: (Name: _ga_CC1B5QY8E3), (Name: _ga) |
| Location | IP: 108.138.26.63; ASN: 16509; Org: Amazon.com, Inc.; City: Frankfurt am Main; Country: DE |
| SSL | Issuer: Amazon / Amazon RSA 2048 M01; Subject: polexbot.pro |
| DNS records | A: 108.138.26.125, 108.138.26.63, 108.138.26.95, 108.138.26.23; NS: ns-95.awsdns-11.com, ns-2036.awsdns-62.co.uk, ns-722.awsdns-26.net, ns-1264.awsdns-30.org; Soa: Nsname: ns-1264.awsdns-30.org; Hostmaster: awsdns-hostmaster.amazon.com; Serial: 1; Refresh: 7200; Retry: 900; Expire: 1209600; Minttl: 86400; Txt: v=spf1 -all |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: SAMEORIGIN; Referrerpolicy: strict-origin-when-cross-origin; Xxssprotection: ✗; Permissionspolicy: camera=(), microphone=(), geolocation=(), payment=(); Xcontenttypeoptions: nosniff; Contentsecuritypolicy: default-src 'self' https: data: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-; Stricttransportpolicy: max-age=31536000; includeSubDomains; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Get IP | IP: 108.138.26.95; Family: 4 |
| Redirects | Chain: https://polexbot.pro, https://www.polexbot.pro/; Count: 1 |
| Page links | External: https://polymarket.com/event/next-french-presidential-election, https://polymarket.com/event/brazil-presidential-election; External count: 2; Internal count: 17 |
| HTTP headers | Headers: Server: nginx; Content type: text/html; charset=UTF-8; X powered by: Express; Strict transport security: max-age=31536000; includeSubDomains; Content security policy: default-src 'self' https: data: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https: wss:; frame-ancestors 'self'; X frame options: SAMEORIGIN; X content type options: nosniff; Referrer policy: strict-origin-when-cross-origin; Permissions policy: camera=(), microphone=(), geolocation=(), payment=(); Via: 1.1 8109fadbc132b410ecc2c3df250d6144.cloudfront.net (CloudFront); X cache: Miss from cloudfront |
PhishDestroy rates polexbot.pro as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-25. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on polexbot.pro. A confirmed blockchain transaction cannot be reversed.
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x06dc51826bc524d9a83770e7de9dd7e005b04524Format validated · Domain analysis0x66ad4221d66358ab9867f6d8cae73ede08e5cc4eFormat validated · Domain analysis0x6916cc00aa1c3e75ecf4081df7cae7d2f3592fd4Format validated · Domain analysis0x76d90685ded3907b5bba8af633812aceca00205aFormat validated · Domain analysis0x76eca4109d0dfe8649d5e3861dfccac67ae7d630Format validated · Domain analysis0x8b4bca1d794779e66e023d44391b2a86c5ab541bFormat validated · Domain analysis0x9bbf8abf929eddbb4da10535cf4c02db33f4c59fFormat validated · Domain analysis0xa19cbababc312f9df185e49d7004c249ed1ade6bFormat validated · Domain analysis0xa9c94c974a34abd275b7d576f14bf955bad543d2Format validated · Domain analysis0xb392b0234600393289f7a5a0dc32af604ea0fc73Format validated · Domain analysisIoC extraction recorded 2026-10-25 05:00 UTC
Last checked
ns-1264.awsdns-30.orgns-2036.awsdns-62.co.ukns-722.awsdns-26.netns-95.awsdns-11.comnsname: ns-1264.awsdns-30.orghostmaster: awsdns-hostmaster.amazon.comserial: 1refresh: 7200retry: 900expire: 1209600minttl: 86400Location describes the IP network.
c9ac600b3e61e970e6fb829868181c596c92bb2bb8e6f4964d64c0cbdc8137edpolexbot.prowww.polexbot.proSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was redirecting visitors elsewhere at the latest check.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
origin.polexbot.proDomain recordwww.polexbot.proDomain recordAn estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 34 SHA-256 hashes: 29 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-10-29 01:58 UTC.
Open this scan on URLScan 01a1715a-4da1-718d-9999-b133425d7cd7 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Our scanner could not complete this check.
polexbot.pro Recorded events: 13. 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 |
|---|
PD-20261025-0A50AD Recipient: abuse@identitydigital.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 ↗
polexbot.pro)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.
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.