chekbot.online is an impersonation phishing domain whose name echoes the "check bot" style of verification tools that crypto communities are used to seeing. PhishDestroy first saw it on 2026-09-04. The site has been offline since 2026-09-11, and it was still unreachable at the last check on 2026-10-19. The live page carried the French LWS hosting placeholder ("Bravo ! Votre domaine chekbot.online a bien été créé avec LWS !"), while our classification is impersonation phishing.
How the scam works
Impersonation pages copy the look and wording of a service the victim already trusts, such as a bot, a wallet or a support desk. The victim is then asked to verify, log in or reconnect. Whatever they type or approve goes to the operators, including passwords, recovery phrases, or a signature on a wallet prompt. A short, slightly misspelled name like chekbot is meant to pass a quick glance in a chat link or a search result.
Evidence
On 2026-09-11, 19 of 89 VirusTotal engines flagged the domain. They included BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, CyRadar and the Vietnamese anti-scam group Chong Lua Dao. Spamhaus lists it in its DBL under the phishing category, which matters because mail filters use that list to block messages carrying the link. Five AlienVault OTX threat pulses reference the domain, so other researchers tracked it independently. It also sits on the PhishDestroy blocklist.
Infrastructure
The domain was registered on 2025-12-11, nearly nine months before PhishDestroy flagged it. Aged domains like this tend to slip past filters that distrust brand-new registrations. Registration and hosting both run through LWS: Ligne Web Services SAS as registrar, and a Groupe LWS SARL server in France at 213.255.195.57. The Let's Encrypt certificate only means the padlock showed. It says nothing about who ran the site.
What to do
If you typed a password or login code on chekbot.online, change that password everywhere you reuse it and turn on app-based two-factor authentication. If you entered a wallet recovery phrase, treat the wallet as compromised and move any remaining funds to a new wallet created on a clean device. Be wary of follow-up messages offering to "recover" losses, because that is a common second-stage scam. Defenders should block the domain and its IP at the DNS and proxy level, and search mail and chat logs for links to it from early September 2026 onward.
RegistrationCreated Dec 11, 2025 (312d)—Expires Dec 11, 2026
Time to First Unavailability6 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 4, 2026
DOM Analysisanalyzed Sep 5, 2026score 83/1001 brand signal
Submitted URLhttp://chekbot.online/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
213.255.195.57
Network ASN
AS210403
Organization
Groupe LWS SARL
Observed location
Golbey, FR
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 4
ns21.lwsdns.com
ns22.lwsdns.com
ns23.lwsdns.com
ns24.lwsdns.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-07-16 06:21:10
Valid until
2026-10-14 06:21:09
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-09-04 22:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint4e044fe7fae33f7f3a2433fd05685dfa74aec5ed383e1d8f22b7fc635f42cebeCertificate names · 1 SANs
www.chekbot.online
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.chekbot.onlineDomain record
The original observation time is not recorded for these hostnames.
Technologies · 4 identified
J
jQuery
JavaScript libraries
jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.
Google Hosted Libraries is a stable, reliable, high-speed, globally available content distribution network for the most popular, open-source JavaScript libraries.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · chekbot.online
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches5
Same favicon hash or the same page title as this host.
6 evidence signal groups linked1 stored notification recordsContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
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.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
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 chekbot.online)
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)
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
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.
