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.
등록 정보생성됨 2025년 12월 23일 (300d)—Expires 2026년 12월 23일
HTTP 상태200
기술 세부 정보Provenance & timestamps
최초 발견2025년 12월 25일
DOM Analysisanalyzed 2026년 3월 11일score 88/1002 brand signals
Submitted URLhttp://lido.exchange/
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-19 01:40:20 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-19 01:40:20 UTClast content: 2026-10-19 01:40:20 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
기술 · 5 identified
N
Node.js
Programming languages
JavaScript runtime built on Chrome V8 engine for server-side development.
E
Envoy
E
Express
H
HSTS
보안
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
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.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
FBI 지침
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.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 lido.exchange)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.
How do phishing scams typically work?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
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)
