VirusTotal
3 / 91 engine detections
レポートを開く“Firelight”
ブロックリスト掲載ドメイン: fireflight.finance — 未検証. 証拠の概要: VirusTotal 3/91 (alphaMountain.ai, CRDF, Gridinsoft); 2 external blocklist matches (MetaMask, SEAL)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 91 engine detections
レポートを開く23 community references
レポートを開くprovider verdict: clean
レポートを開く14 確認済み — ブロックなし
80/100
レポートを開く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
On July 25, 2026, analysis of the domain fireflight.finance confirms a high‑risk, active phishing infrastructure. The domain was registered on February 21, 2026 through NiceNIC International Group Co., Limited and is served by the authoritative nameservers dns1.p01.nsone.net and dns2.p01.nsone.net. DNS resolution points to the IP address 35.157.26.135, which belongs to Amazon.com, Inc. (AS16509) and is geolocated in Germany. The site delivers an HTTP 200 response and presents a valid TLS certificate issued by Let’s Encrypt (E7), with HTTP Strict Transport Security (HSTS) enforced.
Technology fingerprints identify Netlify as the hosting platform and confirm the presence of HSTS. The page title returned by the server is "Firelight," but no further content analysis is available. Security telemetry shows the domain appears on one public blocklist, is actively blocked by PhishDestroy, and received a Gridinsoft trust score of 0 out of 100. VirusTotal scans recorded three positive detections out of ninety‑three scanning engines, indicating that multiple security vendors have identified malicious behavior.
The collected evidence—recent registration, Amazon‑hosted infrastructure, low trust score, positive vendor detections, and active blocklist listings—strongly supports the classification of fireflight.finance as a phishing site. What remains uncertain is the exact payload or credential‑collection mechanism employed, as the page content has not been publicly examined. Defenders should immediately block the domain at network perimeter and proxy layers, add the associated IP address to deny lists, and monitor NS1/NS2 name server queries for related sub‑domains. Ongoing surveillance of VirusTotal and other reputation feeds is recommended to capture any escalation in detection counts or emergence of additional malicious indicators.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x4c18ff3c89632c3dd62e796c0afa5c07c4c1b2b3Format validated · Domain analysisIoC extraction recorded 2026-07-29 02:36:31 UTC
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 の評判はこのドメインに起因しません。
dns2.p01.nsone.netLocation describes the IP network.
a4dbc5275b6e493adc9a6e0f852b320105cae15fb942a57288f2deb8637f5f59Saved 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 fireflight.finance · 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.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
23 community references
View source3/91 engine detections
View sourceNo threat flag
View sourcefireflight.finance
View sourcePage captured
View sourceコミュニティの 1 人が報告・初回確認 2026年2月12日
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
fireflight.finance
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 ↗
fireflight.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.