VirusTotal
16 / 91 engine detections
レポートを開く“403 Forbidden”
Googleなりすまし: web.securefinance.online — コンテンツが利用できません. 証拠の概要: VirusTotal 16/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); Google Safe Browsing…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
16 / 91 engine detections
レポートを開く悪意あり
レポートを開くThreat flag recorded
レポートを開くno community references
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
web.securefinance.online is a phishing site that PhishDestroy classifies as impersonation. It sits on a subdomain whose name suggests a secure financial service, a label meant to win the trust of people managing money or crypto. PhishDestroy first flagged it on 2026-07-27. The site has been offline since 2026-09-08, and its DNS was still inactive when we last checked on 2026-10-19.
Impersonation pages copy the look and wording of a trusted financial or crypto service, then ask visitors to sign in, verify an account or connect a wallet. Anything typed into the fake form goes straight to the operators. That can include usernames, passwords, one-time codes and recovery phrases, which they use to take over accounts and move funds. When we checked, the page returned a "403 Forbidden" title instead of a branded login screen, but the domain is classified as impersonation phishing.
Sixteen of 91 VirusTotal engines flagged the domain as of 2026-08-15. Detections came from established vendors, including BitDefender, ESET, Fortinet, G-Data, alphaMountain.ai, CRDF, CyRadar and Google Safe Browsing. Google Safe Browsing separately lists it under SOCIAL_ENGINEERING, its category for deceptive pages that impersonate legitimate services. That listing triggers warnings in Chrome, Firefox and Safari. The domain is also on the PhishDestroy blocklist.
The domain was registered through NameCheap, Inc. and hosted at 67.217.58.79 on Interserver, Inc. in the United States. It used a free, automatically issued Let's Encrypt certificate, so the padlock in the browser meant only that the connection was encrypted, not that the site was legitimate. The site was active for roughly six weeks after PhishDestroy first flagged it, then went dark when its DNS stopped resolving.
If you entered a password on this site, change it right away on the real service and on any other account where you reused it. Turn on app-based or hardware-key two-factor authentication, and review recent logins and transactions for anything unfamiliar. If you typed in a wallet recovery phrase, treat that wallet as compromised and move any remaining funds to a new wallet created on a clean device. Security teams should block the domain and its hosting IP, search proxy and email logs for visits since 2026-07-27, and reset credentials for any users who reached it.
For the registrable domain securefinance.online behind this subdomain, 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.
vda4700b.trouble-free.netLocation describes the IP network.
3613585eafd7e6dbec017f5f2bedee6a8179b5ec0c807a4a378577f564762089securefinance.onlineSaved 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 web.securefinance.online · checked Aug 13, 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.
web.securefinance.online
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
到達可能→利用不可
15→16
No flag recorded→Flag recorded
到達可能
Threat flag recorded
View source16/91 engine detections
View sourceweb.securefinance.online
View sourceコミュニティ報告:2 件
カテゴリOTHER_INVESTMENT_SCAM
Data submited by Intelligence for good
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 ↗
web.securefinance.online)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.