Scamadviser
1/100
Trust score, lower = worse
Open reportThe captured polexbot.fun page presents an automated trading bot for Polymarket's 5-minute crypto up/down rounds, with a headline reading "Automated Trading on 5 Minute Rounds." The page states that the bot follows live pricing on BTC, ETH, SOL, XRP, DOGE and BNB, taking an up or down position each round within user-defined limits. A "BTC Round Radar" section displays the last 37 rounds as colored blocks with a live countdown timer, and an "Open Dashboard" button appears in the header.
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.
Cloudflare Radar capture · 2026-10-31 22:50 UTC · SHA-256 1c6be1e1…c88be84
PhishDestroy analysis, reviewed version
The captured polexbot.fun page presents an automated trading bot for Polymarket's 5-minute crypto up/down rounds, with a headline reading "Automated Trading on 5 Minute Rounds." The page states that the bot follows live pricing on BTC, ETH, SOL, XRP, DOGE and BNB, taking an up or down position each round within user-defined limits. A "BTC Round Radar" section displays the last 37 rounds as colored blocks with a live countdown timer, and an "Open Dashboard" button appears in the header.
The stored VirusTotal domain result reports 0 detections out of 92 engines.
1/100
Trust score, lower = worse
Open report3 community references
Open reportScan report
Open reportPage capture
SHA-256 2d9868b0…ca7776e
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
25 / 100 · heuristic score · 8 brand references · 0 classifications
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.fun |
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Web archive observations | Last: 2026-10-31T22:16:13Z; First: 2026-10-31T22:16:13Z; Changes: 0; Days archived: 1; Avg page bytes: 96314 |
| Crawler rules | Agents: *; Present: ✓; Sitemaps: https://www.polexbot.fun/sitemap.xml |
| Sitemap | Present: ✓; URL count: 37 |
| Security contact file | Present: ✓; Found in: /.well-known/security.txt |
| Page title and metadata | Ogurl: https://www.polexbot.fun/; Title: Polexbot: Automated Polymarket Bot for 5-Minute Crypto Rounds; Author: Polexbot; Ogtype: website; Robots: index,follow; Ogimage: https://www.polexbot.fun/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.fun/; 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: 23; 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: 5) |
| Forms and mixed content | No sri: https://www.googletagmanager.com/gtag/js; Third party scripts: 1 |
| Status | Up: ✓; Code: 301; Timings: DNS: 99; TLS: 19; Wait: 36; Connect: 6; Download: 0; Response ms: 160 |
| 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: 226469; Co2 grams: 0.0083; Cleaner than: 4 |
| DNS server | NS: (IP: 205.251.193.7; Host: ns-263.awsdns-32.com), (IP: 205.251.195.58; Host: ns-826.awsdns-39.net), (IP: 205.251.196.79; Host: ns-1103.awsdns-09.org), (IP: 205.251.198.101; Host: ns-1637.awsdns-12.co.uk); Zone: polexbot.fun |
| Cookies | Cookies: (Name: _ga_CC1B5QY8E3), (Name: _ga) |
| Location | IP: 18.64.211.72; ASN: 16509; Org: Amazon.com, Inc.; City: Frankfurt am Main; Country: DE |
| SSL | Issuer: Amazon / Amazon RSA 2048 M04; Subject: polexbot.fun |
| DNS records | A: 18.64.211.49, 18.64.211.62, 18.64.211.11, 18.64.211.72; NS: ns-263.awsdns-32.com, ns-1103.awsdns-09.org, ns-826.awsdns-39.net, ns-1637.awsdns-12.co.uk; Soa: Nsname: ns-1637.awsdns-12.co.uk; 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: 18.64.211.49; Family: 4 |
| Redirects | Chain: https://polexbot.fun, https://www.polexbot.fun/; Count: 1 |
| Page links | External: https://polymarket.com/series/btc-up-or-down-5m, https://polymarket.com/event/next-french-presidential-election, https://polymarket.com/event/who-will-be-the-next-prime-minister-of-israel-after-the-next-election; External count: 3; Internal count: 17 |
| Registration record | Registrar: NICENIC INTERNATIONAL GROUP CO., LIMITED; Created: 2026-10-30T08:48:07Z; Updated: 2026-10-30T08:48:38Z; Expires: 2027-10-30T08:48:07Z; Status: clientDeleteProhibited https://icann.org/epp, clientTransferProhibited https://icann.org/epp, addPeriod https://icann.org/epp; Nameservers: ns-1637.awsdns-12.co.uk, ns-826.awsdns-39.net, ns-263.awsdns-32.com, ns-1103.awsdns-09.org |
| 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 9e1bdbb4be4368260f133aad2ba67de2.cloudfront.net (CloudFront); X cache: Miss from cloudfront |
PhishDestroy rates polexbot.fun as critical risk (evidence score 71/100) from the recorded evidence; it was first recorded on 2026-10-31. 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.fun. 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 analysis0x2e4d05beafd81a6e85bc0c6a94820d61ef34f703Format validated · Domain analysis0x35fa2bb1d86efdaf39abe1c8787f5cf25f252bd4Format validated · Domain analysis0x6916cc00aa1c3e75ecf4081df7cae7d2f3592fd4Format validated · Domain analysis0x6db983ff1cbc85249e64e6ccd101aaa613ba4ab5Format validated · Domain analysis0x84d3e37ad85b7ce551b0b4d6bb9c19551f73b286Format validated · Domain analysis0xa9c94c974a34abd275b7d576f14bf955bad543d2Format validated · Domain analysis0xcc500cbcc8b7cf5bd21975ebbea34f21b5644c82Format validated · Domain analysis0xe734e7bf7cfb9e464681f71822f6c2f6be514f0cFormat validated · Domain analysis0xede186f37ead91aa618cf8101db2bfe6b6c57dd1Format validated · Domain analysisIoC extraction recorded 2026-11-01 05:00 UTC
Last checked
1c6be1e1…c88be84 SHA-256 of the prepared copy given to the model: 49477e06…b46cc6b 1c6be1e113d102d5f7555a4683a6e493c2e3994ddc054cdd1c6c34adfc88be84 · 692912 bytes 3d098a03b3e95cb5383626e8fbd6da3570aefeb65ab06d5dcc908159857da071 · 766696 bytes e3546720b8289939c63fddb0d2c31c6a3602908d4f05e8649d9e6e39cf2e585e · 749787 bytes e6bab21917fa9268b31a6bdbfd3d895b5c01dec69e83ebdc5ece6d5ed2c6809f · 762723 bytes For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
ns-1103.awsdns-09.orgns-1637.awsdns-12.co.ukns-263.awsdns-32.comns-826.awsdns-39.netnsname: ns-1637.awsdns-12.co.ukhostmaster: awsdns-hostmaster.amazon.comserial: 1refresh: 7200retry: 900expire: 1209600minttl: 86400Location describes the IP network.
05c366d4f88b32e47adab35e95279a929c0f4dbc521540bf4c78dbe3d499360bpolexbot.funwww.polexbot.funSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The domain no longer resolves in DNS.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
origin.polexbot.funDomain recordwww.polexbot.funDomain recordGoogle PageSpeed Insights — mobile performance audit of polexbot.fun ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://polexbot.fun/https://www.polexbot.fun/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-8Sat, 31 Oct 2026 22:16:28 GMTW/"374a5-1a193996f22"Sat, 31 Oct 2026 20:14:28 GMTcamera=(), microphone=(), geolocation=(), payment=()strict-origin-when-cross-originnginxmax-age=31536000; includeSubDomainschunkedAccept-Encoding1.1 4bc6e08d9495b312ae3b91e801107f80.cloudfront.net (CloudFront)Q9CLXV_owOaOKPksJ6mdKRsT5gPdGTDCmuRpD-9-q2QhXcc2useP_Q==CDG50-P4Miss 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: 34 SHA-256 hashes: 32 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-31 22:18 UTC.
Open this scan on URLScan 01a19406-1932-70a9-9b43-13987f8b6350 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Recorded events: 12. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
polexbot.fun 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.fun)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.