The domain lido.website is a confirmed phishing site engaged in brand impersonation targeting Lido, a cryptocurrency platform. It poses an elevated risk as a cryptocurrency scam designed to deceive users into interacting with fraudulent services, though no drainer kit was identified. The site is currently taken offline, reducing immediate exposure, but prior activity suggests it was actively used for malicious purposes.
Technical indicators confirm lido.website was flagged by 2 of 95 VirusTotal security vendors, including CRDF and Gridinsoft. It appears on 1 security blocklist (PhishDestroy) but was not flagged by Google Safe Browsing. The domain was registered through NameCheap, Inc. on February 21, 2026, and resolves to the IPv6 address 2606:4700:3033::6815:51ac, hosted by Cloudflare in the US. The SSL certificate was issued by Google Trust Services / WE1, and the site employed Cloudflare and HTTP/3 technologies. The observed page title was 'lido.website | 522: Connection timed out', consistent with its current offline status.
Users who interacted with lido.website should immediately revoke any token approvals associated with the site and transfer funds to a new wallet to prevent unauthorized access. Report the domain to relevant platforms, including the impersonated brand (Lido), the registrar (NameCheap), and anti-phishing organizations such as PhishTank or the Anti-Phishing Working Group. Enable two-factor authentication on all cryptocurrency accounts and monitor for unauthorized transactions or login attempts.
DOM Analysisanalyzed 2026年7月11日score 81/1001 brand signal
Favicon Hash
ICANN OVERSIGHT
認定と RAA の背景
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
