VirusTotal
15 / 91 engine detections
レポートを開く“Google”
Lidoなりすまし: liido.finance — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 15/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Emsisoft); Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 91 engine detections
レポートを開くDBL_PHISH
17 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 the domain liido.finance indicates active brand impersonation targeting Lido, a known decentralized finance platform. The domain was registered on May 26, 2026, through NICENIC INTERNATIONAL GROUP CO., LIMITED, and currently resolves to the IP address 142.251.155.119, which is associated with AS13335 (Cloudflare, Inc.) in the United States. Infrastructure analysis reveals the use of Cloudflare nameservers (lady.ns.cloudflare.com and vick.ns.cloudflare.com), alongside technologies such as Google Web Server, HSTS, and HTTP/3. The domain returns an HTTP 301 redirect status, though the destination remains unconfirmed. The page title is reported as 'Google,' which does not align with the expected branding of Lido, suggesting either obfuscation or incomplete deployment of the phishing infrastructure. Detection data shows the domain has been flagged by at least three security blocklists, including PhishDestroy, MetaMask, and SEAL. AlienVault OTX records the domain in four threat intelligence pulses, further corroborating its malicious classification. Six of 91 security vendors on VirusTotal have identified the domain as malicious, though the specific nature of the threat—whether credential harvesting, token theft, or another attack vector—remains unconfirmed due to the lack of direct page analysis. The SSL certificate is issued by Let's Encrypt, a common choice for both legitimate and malicious domains. Defenders are advised to treat this domain as high-risk, particularly in environments where Lido or similar decentralized finance platforms are in use. Network-level blocking of the IP 142.251.155.119 and the domain liido.finance is recommended, alongside monitoring for related infrastructure leveraging the same registrar or hosting provider. Further investigation into the redirect chain and any associated wallet addresses or backend infrastructure may provide additional indicators of compromise.
Last checked
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 の評判はこのドメインに起因しません。
lady.ns.cloudflare.comvick.ns.cloudflare.comLocation describes the IP network.
57badfb46d0118c5741b246462641aa5995f17e1d6843613df745a5821625692Saved 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 liido.finance · checked Jun 26, 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.
redirect: raw=redirect_301; http=301; via=https_proxy; location=https://st-english-site.eu.cc?f=bGlpZG8uZmluYW5jZQ; server=cloudflare
liido.finance
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
redirected
http_redirect
利用不可→到達可能
到達可能→利用不可
利用不可→到達可能
到達可能→利用不可
利用不可→到達可能
到達可能→利用不可
到達可能→利用不可
1→6
17 community references
View source15/91 engine detections
View sourceNo threat flag
View sourcePage captured
View sourceliido.finance
View source保存された類似ドメイン:30 件
コミュニティの 1 人が報告・初回確認 2026年5月28日
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 ↗
liido.finance)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.