Scamadviser
11/100
Trust score, lower = worse
Open reportPhishDestroy first recorded polexbot.net on 2026-10-23. 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@vsys.name. The latest stored availability evidence still shows the domain reachable; 1 month 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
PhishDestroy’s automated assessment classified polexbot.net as an impersonation phishing page. The recorded page title “Polexbot: Automated Polymarket Bot for 5‑Minute Crypto Rounds” shows the site pretends to provide a Polymarket bot. The domain was first seen by PhishDestroy on 2026-10-23. When checked on 2026-10-26 the site returned an HTTP 301 redirect to the www subdomain.
Impersonation phishing copies the branding and terminology of a legitimate service to lure users into entering login credentials or granting cryptocurrency wallet permissions. The promise of rapid profit from an automated bot encourages victims to act without verifying the site’s authenticity, allowing attackers to harvest the submitted information.
VirusTotal scanned the domain on 2026-10-26 with 92 engines and reported zero detections. Google Safe Browsing checked on 2026-10-26 and did not flag the site. urlscan analysis on 2026-10-23 marked the page as malicious in its engine verdict with a score of 51, while the overall verdict was non‑malicious. OTX listed four pulses for polexbot.net as of 2026-10-26, and external blocklists MetaMask and SEAL also contain the domain. PhishDestroy’s internal blocklist marked the domain as malicious on 2026-10-26.
The domain was registered on 2026-10-22 (recorded creation on 2026-10-23) through SOLLUTIUM LLC (Sollutium EU sp. z o.o.). DNS resolution returned the IP address 99.84.152.80, which belongs to Amazon’s US network. The TLS certificate issued by Amazon RSA 2048 M01 is valid from 2026-10-23 to 2027-05-08.
Anyone who may have entered Polymarket credentials on polexbot.net should change those credentials and enable any available two‑factor authentication. Organizations should add polexbot.net to web‑filter blocklists and monitor logs for connections to the recorded IP address. Continue to monitor the domain and related indicators for any changes in behavior.
11/100
Trust score, lower = worse
Open report4 community references
Open reportScan report
Open reportPage capture
SHA-256 b37bea7c…0532430
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
10 / 100 · heuristic score · 7 brand references · 1 classification
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative 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.net |
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Web archive observations | Last: 2026-10-23T12:43:44Z; First: 2026-10-23T12:43:44Z; Changes: 0; Days archived: 1; Avg page bytes: 78896 |
| Crawler rules | Agents: *; Present: ✓; Sitemaps: https://www.polexbot.net/sitemap.xml |
| Sitemap | Present: ✓; URL count: 30 |
| Security contact file | Present: ✓; Found in: /.well-known/security.txt |
| Page title and metadata | Ogurl: https://www.polexbot.net/; Title: Polexbot: Automated Polymarket Bot for 5-Minute Crypto Rounds; Author: Polexbot; Ogtype: website; Robots: index,follow; Ogimage: https://www.polexbot.net/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.net/; 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: 31; TLS: 11; Wait: 34; Connect: 6; Download: 1; Response ms: 83 |
| 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: 184541; Co2 grams: 0.0067; Cleaner than: 9 |
| DNS server | NS: (IP: 205.251.195.247; Host: ns-1015.awsdns-62.net), (IP: 205.251.196.12; Host: ns-1036.awsdns-01.org), (IP: 205.251.198.192; Host: ns-1728.awsdns-24.co.uk), (IP: 205.251.192.232; Host: ns-232.awsdns-29.com); Zone: polexbot.net |
| Cookies | Cookies: (Name: _ga_CC1B5QY8E3), (Name: _ga) |
| Location | IP: 99.84.152.81; ASN: 16509; Org: Amazon.com, Inc.; City: Frankfurt am Main; Country: DE |
| SSL | Issuer: Amazon / Amazon RSA 2048 M01; Subject: polexbot.net |
| DNS records | A: 99.84.152.69, 99.84.152.81, 99.84.152.80, 99.84.152.119; NS: ns-1036.awsdns-01.org, ns-232.awsdns-29.com, ns-1015.awsdns-62.net, ns-1728.awsdns-24.co.uk; Soa: Nsname: ns-1036.awsdns-01.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: 99.84.152.80; Family: 4 |
| Redirects | Chain: https://polexbot.net, https://www.polexbot.net/; Count: 1 |
| Subdomains | Count: 1; Subdomains: www.polexbot.net |
| Page links | External: https://polymarket.com/event/next-french-presidential-election, https://polymarket.com/event/brazil-presidential-election; External count: 2; Internal count: 16 |
| Registration record | Registrar: Sollutium EU sp. z o.o.; Created: 2026-10-22T23:25:32Z; Updated: 2026-10-23T07:50:27Z; Expires: 2027-10-22T23:25:32Z; Status: ok https://icann.org/epp; Nameservers: ns-1015.awsdns-62.net, ns-1036.awsdns-01.org, ns-1728.awsdns-24.co.uk, ns-232.awsdns-29.com |
| 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 bc7c353da4431a6dd3688d01f8a48b98.cloudfront.net (CloudFront); X cache: Miss from cloudfront |
PhishDestroy rates polexbot.net as critical risk (evidence score 86/100) from the recorded evidence; it was first recorded on 2026-10-23. 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.net. 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 analysis0x4aba910be73fbaf43d2c8abdca7b8bb4533bf791Format validated · Domain analysis0x50c9261511205e9ad726dd2cca2fea2618218ae1Format validated · Domain analysis0x89f8cb122649ad2e73b46c6990bd39b6517868f5Format validated · Domain analysis0xb6fef4c2c436ab8bbf07d017952e851dcf717394Format validated · Domain analysis0xd6b6d5b462dd651ffdb2e54e61a951979de3793fFormat validated · Domain analysis0xdfddd5c3b996c4176d72c3ca7859f10a7c825585Format validated · Domain analysis0xe392d6cc6a012f306cef646f79114eb6f351c023Format validated · Domain analysis0xe9c6312464b52aa3eff13d822b003282075995c9Format validated · Domain analysis0xf705fa045201391d9632b7f3cde06a5e24453ca7Format validated · Domain analysisIoC extraction recorded 2026-10-24 04:00 UTC
Last checked
ns-1015.awsdns-62.netns-1036.awsdns-01.orgns-1728.awsdns-24.co.ukns-232.awsdns-29.comnsname: ns-1036.awsdns-01.orghostmaster: awsdns-hostmaster.amazon.comserial: 1refresh: 7200retry: 900expire: 1209600minttl: 86400Location describes the IP network.
db0ebacca8864099f6758f305e13624012947767b14d8fb757c7fe7d778bba26polexbot.netwww.polexbot.netSaved 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.
www.polexbot.netDomain recordGoogle PageSpeed Insights — mobile performance audit of polexbot.net ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://polexbot.net/https://www.polexbot.net/Content-Type: text/html; charset=UTF-8Server: nginxContent-Encoding: gzipX-Powered-By: ExpressCache-Control: public, max-age=0summary_large_imageh3=":443"; ma=86400public, max-age=0keep-alivegzipdefault-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'text/html; charset=UTF-8Fri, 23 Oct 2026 12:43:44 GMTW/"2d0dd-1a167bfdc5b"Fri, 23 Oct 2026 07:53:09 GMTcamera=(), microphone=(), geolocation=(), payment=()strict-origin-when-cross-originnginxmax-age=31536000; includeSubDomainschunkedAccept-Encoding1.1 eb465fe6664935c15ab89d748bafa23a.cloudfront.net (CloudFront)TbElHz7B2qu6iL_wtFbOjrm54NODNrBXSn8gkaA0lPfYeTBRfWrzYg==DUS51-P7Miss from cloudfrontnosniffSAMEORIGINExpressValues 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: 32 SHA-256 hashes: 22 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:59 UTC.
Open this scan on URLScan 01a168c6-4fc1-7681-8012-ccf83cdd8474 ↗
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.net Recorded events: 16. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 13 h 18 min after registration
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-20261023-E96E38 Recipient: abuse@vsys.name 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.net)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.