VirusTotal
5 / 89
“PolyBot — Polymarket Trading Bot”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@godaddy.com.
The latest stored availability evidence still shows the domain reachable; 2 months 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.
5 / 89
DBL_PHISH
checked — no detections recorded
Report4 community references
Reportprovider verdict: clean
Reportstored report
Report Analysis completed
Report80/100
ReportChecked; no threat flag recorded
ReportPhishDestroy first observed polybot.technology on Aug 8, 2026. Stored content metadata identifies Chainlink as the apparent target. The captured page title is “PolyBot — Polymarket Trading Bot”. Page analysis recorded additional brand references to MetaMask. Stored page analysis classifies the content as crypto drainer. Current evidence score: 88/100 (critical).
Positive findings are stored from 2 sources: VirusTotal and Spamhaus DBL. VirusTotal recorded 5 detections among 89 engines: ChainPatrol, alphaMountain.ai, ESET, Gridinsoft, SOCRadar on Sep 21, 2026 at 02:06 UTC. Spamhaus DBL: DBL_PHISH on Oct 7, 2026 at 22:30 UTC. Additional recorded evidence: AlienVault OTX listed 4 community pulse references (not vendor detections) on Oct 5, 2026 at 12:01 UTC.
HTTP 200 was recorded on Oct 11, 2026 at 22:11 UTC. Latest classified outcome: live content observed; cause content served on Oct 11, 2026 at 20:11 UTC. Registration records for the domain list GoDaddy.com, LLC as the registrar and Jul 31, 2026 as the creation date. Registration preceded first observation by 7 days. At collection time, the hostname resolved to 76.76.21.21 on AS16509 (AMAZON-02 - Amazon.com, Inc., US). The IP and ASN identify shared Vercel edge infrastructure; the origin server is not established by this address. DOM analysis on Aug 8, 2026 at 14:20 UTC returned 88/100. The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and URLQuery. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Apr 10, 2027; checked Oct 10, 2026 at 16:03 UTC.
The content indicators and 2 positive source findings support the current Chainlink-themed crypto drainer classification.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: alive_content: raw=ok; http=200; via=https_proxy
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.
Edge-IP reputation is not attributed to this domain.
ns65.domaincontrol.comns66.domaincontrol.comLocation describes the IP network.
27177c5f24eb06c7fb023ae1ba680396ca035796890468a9bb009c5c5c0b291eSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of polybot.technology · checked Aug 8, 2026
76.76.21.21. 28 recorded events. 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.
PD-20260808-3CAAE5 Recipient: abuse@godaddy.com Registrar: GoDaddy.com LLC (United States) Policy Violations: Universal TOS + Abuse Policy prohibit fraudulent, abusive, malicious, phishing and illegal activity; grants right to terminate or suspend services Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
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