Skip to security report
polexbot.pro favicon
Domain security and threat intelligence

polexbot.pro

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

PhishDestroy 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”

More about the sources
Recorded security signals

Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

Spamhaus DBL: spam domain Stored blocklist matches: 2
Registrar
RussiaNiceNIC
Resolved IP
Germany108.138.26.63Amazon.com, Inc.
First seen by PhishDestroy
2026-10-25
URLQuery
detections
OTX
community references
Page captures
open gallery
Reports sent
view timeline
OTX: 4 refs 2026-10-25 1 Report Sent

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.

ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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.

Elapsed since first report
28 days
Reports sent
1
Latest case ID
PD-20261025-0A50AD
Current status
HTTP 301 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded polexbot.pro on 2026-10-25. Listed by external blocklists: MetaMask, SEAL. Risk: critical (evidence score 100/100). Registrar: NiceNIC. Status: Last known active. Hosting: Amazon.com, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
Blocklist matches
2 external + PhishDestroy list
Scam type (automated label)
Impersonation
Hosting
Germany108.138.26.63Amazon.com, Inc.
Registrar
RussiaNiceNIC
OTX
4 community refs
Page captures
6

PhishDestroy analysis, earlier unreviewed version

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Source evidenceOTX 4 references 8 sources

Spamhaus DBL

spam domain

OTX

4 community references

Open report

URLScan

Page capture

Open report
URLScanOriginal source recordObserved: 23 fields
Separate monitor record

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a16d36-6919-779d-8caa-5f2b65ebe9b6
Enriched at
2026-10-25T09:11:41Z
Source timestamps
Urlscan enriched at: 2026-10-25 10:11:41

PhishDestroy DOM

90 / 100 · heuristic score · 7 brand references · 1 classification

Content heuristic only; not the final score

Open report
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
polexbot.pro — Polymarket impersonation bot scam
AI description
PhishDestroy assesses polexbot.pro as an impersonation phishing page posing as an automated Polymarket trading bot.
AI summary
Overview 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. How the scam works 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. Evidence 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. Infrastructure 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. What to do 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. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a1715a-4da1-718d-9999-b133425d7cd7/ Cloudflare Radar report: https://radar.cloudflare.com/scan/394a5704-0d49-4790-8a84-898d14a297e3 URLQuery report: https://urlquery.net/report/78ae276c-abc7-4352-adee-5f221fc08b7b Stored capture screenshot: https://urlscan.io/screenshots/01a1715a-4da1-718d-9999-b133425d7cd7.png Cloudflare Radar screenshot (2026-10-25T04:38:17Z): https://screenshots.phishdestroy.io/cf/394a5704-0d49-4790-8a84-898d14a297e3.png URLQuery screenshot: https://screenshots.phishdestroy.io/uq/78ae276c-abc7-4352-adee-5f221fc08b7b.png URLScan screenshot (2026-10-24T09:21:13Z): https://screenshots.phishdestroy.io/us/01a16d36-6919-779d-8caa-5f2b65ebe9b6.png URLScan capture report: https://urlscan.io/result/01a16d36-6919-779d-8caa-5f2b65ebe9b6/ URLScan screenshot (2026-10-25T04:54:11Z): https://screenshots.phishdestroy.io/us/01a17168-9fe8-7695-92e8-9ea565a1feb5.png URLScan capture report: https://urlscan.io/result/01a17168-9fe8-7695-92e8-9ea565a1feb5/ VirusTotal report: https://www.virustotal.com/gui/domain/polexbot.pro Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=polexbot.pro Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
AI generated by
mimo-flash
AI generated at
2026-10-26T21:27:53Z
Revision
5069f9ed196087c8ba9dec12a414c1ca69e0fce9b18ecb1a16287af760159e74
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.

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: 8 fields
Open complete records
Website checksOriginal source recordRetrieved: 25 fields

Mail configuration

SPF record
v=spf1 -all
DMARC
Yes
SPF lookups
0

CAA records

Domain
polexbot.pro

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://www.polexbot.pro/sitemap.xml

Sitemap

Present
Yes
URL count
31

Security contact file (security.txt)

Present
Yes
Found at
/.well-known/security.txt

Page title and metadata

Open Graph URL
https://www.polexbot.pro/
Page title
Polexbot: Automated Polymarket Bot for 5-Minute Crypto Rounds
Author
Polexbot
Open Graph type
website
Indexing directives
index,follow
Open Graph image
https://www.polexbot.pro/og-image.jpg
Open Graph title
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
Open Graph site name
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.
Twitter card
summary_large_image
Canonical URL
https://www.polexbot.pro/
Open Graph description
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
Observed services
  • 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

Scripts without SRI
  • https://www.googletagmanager.com/gtag/js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
301
Request timings, ms
DNS
29
TLS
12
Waiting
15
Connection
14
Download
0
Response time, ms
70

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
208908
CO₂, grams
0.0076
Cleaner than, %
6

DNS servers

Nameservers
  • IP address
    205.251.192.95
    Host
    ns-95.awsdns-11.com
  • IP address
    205.251.196.240
    Host
    ns-1264.awsdns-30.org
  • IP address
    205.251.199.244
    Host
    ns-2036.awsdns-62.co.uk
  • IP address
    205.251.194.210
    Host
    ns-722.awsdns-26.net
DNS zone
polexbot.pro

Cookies

Cookies
  • Name
    _ga_CC1B5QY8E3
  • Name
    _ga

Location

IP address
108.138.26.63
ASN
16509
Organization
Amazon.com, Inc.
City
Frankfurt am Main
Country
DE

TLS certificate

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
Primary nameserver
ns-1264.awsdns-30.org
Hostmaster
awsdns-hostmaster.amazon.com
Serial
1
Refresh, seconds
7200
Retry, seconds
900
Expiry, seconds
1209600
Minimum TTL, seconds
86400
TXT
  • v=spf1 -all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
camera=(), microphone=(), geolocation=(), payment=()
X-Content-Type-Options
nosniff
Content-Security-Policy
default-src 'self' https: data: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-
Strict-Transport-Security
max-age=31536000; includeSubDomains
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
108.138.26.95
IP version
4

Redirects

Redirect chain
  • https://polexbot.pro
  • https://www.polexbot.pro/
Count
1

Page links

External link addresses
  • https://polymarket.com/event/next-french-presidential-election
  • https://polymarket.com/event/brazil-presidential-election
External links
2
Internal links
17

HTTP headers

Response 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
Original source fields · JSON
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
Security Signals
SA Scamadviser Warnings 1/100
This website does not have many visitors We detected cryptocurrency services which can be high risk We could not find a valid SSL certificate while the site offers financial services
DNSFilter considers this website safe
Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Questions about polexbot.pro

Is polexbot.pro legit?

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.

Is polexbot.pro safe to connect a wallet?

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.

What should I do if I used polexbot.pro?

  • 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
  • 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
  • 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
  • Downloaded a file — do not open it and scan the device with security software

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.

Explore

Extracted from stored page analysis

Observed indicators

10 wallet · 0 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

ETH
0x06dc51826bc524d9a83770e7de9dd7e005b04524Format validated · Domain analysis
ETH
0x66ad4221d66358ab9867f6d8cae73ede08e5cc4eFormat validated · Domain analysis
ETH
0x6916cc00aa1c3e75ecf4081df7cae7d2f3592fd4Format validated · Domain analysis
ETH
0x76d90685ded3907b5bba8af633812aceca00205aFormat validated · Domain analysis
ETH
0x76eca4109d0dfe8649d5e3861dfccac67ae7d630Format validated · Domain analysis
ETH
0x8b4bca1d794779e66e023d44391b2a86c5ab541bFormat validated · Domain analysis
ETH
0x9bbf8abf929eddbb4da10535cf4c02db33f4c59fFormat validated · Domain analysis
ETH
0xa19cbababc312f9df185e49d7004c249ed1ade6bFormat validated · Domain analysis
ETH
0xa9c94c974a34abd275b7d576f14bf955bad543d2Format validated · Domain analysis
ETH
0xb392b0234600393289f7a5a0dc32af604ea0fc73Format validated · Domain analysis

IoC extraction recorded 2026-10-25 05:00 UTC

Blocklist matches2 external + PhishDestroy list · MetaMask · PhishDestroy · SEAL 2
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Page captures (6)

All capture links and hashes (6)
polexbot.pro: Crypto scam — Blocked by MetaMask, flagged by SEAL, Spamhaus DBL, 6/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card polexbot.pro: Crypto scam — Blocked by MetaMask, flagged by SEAL, Spamhaus DBL, 6/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v eff4050aa871

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 97 report ↗
IP Reputation Germany108.138.26.63 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing. 0 reports checked 2026-10-25
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar NiceNIC RU(RU) PhishDestroy Investigation
Abuse contactabuse@nicenic.net
RegistrationExpires 2027-10-24
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First Detected2026-10-25
DOM Analysisanalyzed 2026-10-25score 90/1007 brand signals
IoC Extractionscanned 2026-10-2510 wallet · 0 Telegram IoCs
Submitted URLhttp://polexbot.pro/
Favicon Hash
Case ID
Observed page title
Polexbot: Automated Polymarket Bot for 5-Minute Crypto Rounds
Automated brand references
Across Ankr Celer MetaMask Near Signal Ups
TLS Certificate
Issued by Amazon / Amazon RSA 2048 M01 · stored validity ends in 168 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany108.138.26.63
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
Amazon.com, Inc.
Observed location
GermanyFrankfurt am Main, DE
Server header
nginx

Nameservers 4

  • ns-1264.awsdns-30.org
  • ns-2036.awsdns-62.co.uk
  • ns-722.awsdns-26.net
  • ns-95.awsdns-11.com

SOA

  • nsname: ns-1264.awsdns-30.org
  • hostmaster: awsdns-hostmaster.amazon.com
  • serial: 1
  • refresh: 7200
  • retry: 900
  • expire: 1209600
  • minttl: 86400

Location describes the IP network.

TLS certificate

Issuer
Amazon / Amazon RSA 2048 M01
Valid from
2026-10-24 00:00:00
Valid until
2027-05-09 23:59:59
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintc9ac600b3e61e970e6fb829868181c596c92bb2bb8e6f4964d64c0cbdc8137ed
Certificate names · 2 SANs
  • polexbot.pro
  • www.polexbot.pro

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

Latest Classified Outcome 2026-11-22 11:59 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved Registration: Active
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-22 11:59 UTC
RDAP registration Active NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765 RDAP HTTP 200 source: Rdap Status Collector AddperiodclientDeleteProhibitedclientTransferProhibited expires 2027-10-24 05:59 UTC checked 2026-10-26 05:36 UTC
Observed timeline last reachable: 2026-11-22 11:59 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.
Recorded subdomains2

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • origin.polexbot.proDomain record
  • www.polexbot.proDomain record
Technologies · 9 identified
Open complete records
Registration & observation details9

Registration evidence

RDAP statuses
addperiod · clientdeleteprohibited · clienttransferprohibited
RDAP response
200
Registrar in registration evidence
NICENIC INTERNATIONAL GROUP CO., LIMITED
Registrar IANA ID
3765
Expiration recorded by RDAP
Registration observation
Registration source
rdap_status_collector

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

All stored data122
Open complete records

Captured network requests

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 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
Polexbot: Automated Polymarket Bot for 5-Minute Crypto Rounds
Crawler
301 Moved Permanently
polexbot.pro
Stored observation history25
Open complete records
All retained availability observations134
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

Recorded events: 13. 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
    polexbot.pro detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Blocklist Detection · OTX Community References · Registrar Context: NiceNIC · Automated brand label: Polymarket · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Identitydigital. Abuse contacts: 1.
    • abuse@identitydigital.com
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Added to PhishDestroy
  2. First abuse report sent+28 min
  1. AlienVault OTX

    4 community references

    +15 min
  2. Abuse report sent

    PD-20261025-0A50AD · Receipt 82841

    abuse@identitydigital.com
    +19 min
  3. URLScan

    Page captured

    +9 min
  4. Added to PhishDestroy

    polexbot.pro

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

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261025-0A50AD Recipient: abuse@identitydigital.com
Page title stored with report: Polexbot: Automated Polymarket Bot for 5-Minute Crypto Rounds
PDF notice generated
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 polexbot.pro)
  • 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.

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.

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/polexbot.pro"
  title="PhishDestroy threat report for polexbot.pro"
  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>