VirusTotal
5 / 91 engine detections
Відкрити звіт“Parking Page”
підробка під Lido: lido.exchange — Останній відомий активний (HTTP 200). Зведення доказів: VirusTotal 5/91 (ChainPatrol, alphaMountain.ai, Chong Lua Dao…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
5 / 91 engine detections
Відкрити звіт2/14
24 community references
Відкрити звітprovider verdict: clean
Відкрити звітNo threat flag
Відкрити звітNo malicious flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis of lido.exchange shows an active infrastructure that is deliberately crafted to masquerade as the Lido brand. The domain was registered on 23 December 2025 through Spaceship, Inc. and resolves to the Amazon‑owned IP address 54.149.79.189, which is associated with ASN 16509 in the United States. The hosting environment reports Node.js, Envoy, Express, HSTS and Akamai components, indicating a modern web stack possibly used to serve dynamic content. The DNS configuration uses the authoritative nameservers launch1.spaceship.net and launch2.spaceship.net, both belonging to the same registrar. The SSL certificate is issued by Go Daddy Secure Certificate Authority – G2 and is currently valid, which can help the site appear legitimate to unsuspecting users.
An HTTP request returns status 200 and the page title is “Parking Page”, suggesting the site is either in a placeholder state or deliberately minimal to avoid detection. The domain has been flagged by PhishDestroy and appears on one additional security blocklist, and six of ninety‑three VirusTotal scanners have raised alerts, reflecting moderate detection confidence. Gridinsoft assigns a trust score of 0 out of 100, reinforcing the malicious classification. The site is categorized as a crypto scam, consistent with the brand impersonation of Lido, a well‑known staking service. Uncertainty remains regarding the exact payload or credential‑harvesting mechanisms because no page content has been captured, and the simple parking page provides no further technical indicators.
Defenders should immediately block traffic to lido.exchange at the network perimeter, add the associated IP 54.149.79.189 to any threat‑intelligence feeds, and monitor for similarly named domains that resolve to the same hosting provider. Continuous TLS inspection is advised to detect any future changes in the certificate or payload delivery.
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.
launch1.spaceship.netlaunch2.spaceship.netLocation describes the IP network.
924019eaf31d54f2df0ea30b9a15c9d172b391de98e70097c15b4bc3e9352292Saved 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 lido.exchange · checked Mar 2, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy
lido.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
6→8
No threat flag
View source24 community references
View source5/91 engine detections
View sourcePage captured
View sourcelido.exchange
View sourceЗбережено 30 схожих доменів
Повідомив 1 учасник спільноти; уперше помічено 25.12.2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
Choose 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 ↗
lido.exchange)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.