VirusTotal
6 / 91 engine detections
レポートを開くLayerZeroなりすまし: dashboard-layerzero.network — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 91 engine detections
レポートを開くDBL_PHISH
23 community references
レポートを開く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
The domain dashboard-layerzero.network was registered on March 26, 2026, through Dynadot Inc and is currently active. Infrastructure analysis reveals it resolves to the IP address 104.21.8.230, hosted behind Cloudflare in Canada, with nameservers eleanor.ns.cloudflare.com and jakub.ns.cloudflare.com. The domain is flagged for brand impersonation targeting LayerZero, a classification supported by its inclusion in one AlienVault OTX threat intelligence pulse and its presence on one security blocklist. The page title 'Just a moment...' suggests a Cloudflare interstitial or a placeholder state, though the exact content remains unanalyzed. The domain is categorized as a streaming scam, though specific details of the fraudulent scheme are not yet confirmed. Six of 94 security vendors on VirusTotal detect this domain as malicious, indicating moderate but not universal consensus on its threat status. The SSL certificate is issued by Let's Encrypt (serial number E7), a common choice for both legitimate and malicious sites. The HTTP status code 403 (Forbidden) may indicate restricted access or defensive measures by the hosting provider. Gridinsoft assigns the domain a trust score of 0/100, reflecting high-risk indicators. Defenders should treat this domain as active phishing infrastructure. Blocking at the DNS or network level is recommended, particularly for organizations associated with LayerZero or those vulnerable to streaming-related fraud. Further investigation into associated IP ranges, certificate histories, and any linked domains may reveal additional malicious infrastructure. No evidence currently suggests this domain is part of a larger campaign, but its registration age and Cloudflare hosting are consistent with evasion tactics observed in similar scams.
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 の評判はこのドメインに起因しません。
jakub.ns.cloudflare.comLocation describes the IP network.
6680f746849cf4d839049f01f4fe3487f74c26375cade2b1e4a8d75ecc70dd61Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
dashboard-layerzero.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
No threat flag
View source23 community references
View source6/91 engine detections
View sourcedashboard-layerzero.network
View sourceコミュニティの 1 人が報告・初回確認 2026年3月26日
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 ↗
dashboard-layerzero.network)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.