VirusTotal
14 / 89 engine detections
レポートを開く認証情報フィッシング: zenpay.finance — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 14/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); PhishDestroy…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
14 / 89 engine detections
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開くNo threat flag
レポートを開くPage capture
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain zenpay.finance was observed on a single security blocklist and is currently listed as blocked by the PhishDestroy feed. VirusTotal records indicate that the domain was submitted for analysis on multiple occasions, with a total of 91 AV engines evaluating the associated URL; none of the engines returned a positive classification at the time of scanning. The presence on a blocklist combined with the absence of detections suggests that the domain is being used for malicious purposes that have not yet been captured by signature‑based scanners.
The threat type is catalogued as generic phishing, which typically involves credential‑harvesting pages designed to impersonate legitimate financial services. No additional infrastructure details such as IP address, ASN, hosting provider, SSL certificate information, or HTTP response codes have been disclosed in the available intelligence, leaving the underlying hosting environment uncertain. Defenders should treat zenpay.finance as a high‑confidence indicator of compromise.
Recommended actions include adding the domain to outbound and inbound firewall deny lists, updating DNS filtering policies to block resolution, and monitoring network traffic for any connections to the domain or its resolved IP addresses. Continuous re‑evaluation is advised, as further analysis may reveal additional artifacts such as malicious payloads, command‑and‑control endpoints, or credential‑stealing forms. Until a more complete profile is established, organisations should assume the domain is actively engaged in credential‑collection activities and enforce strict user awareness controls around unsolicited financial communications.
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 の評判はこのドメインに起因しません。
jen.ns.cloudflare.comyadiel.ns.cloudflare.comLocation describes the IP network.
a7ef831ccabe500ce849cc74997c6597ae34f798c63c6ab35cca425b7f8f16e3Saved 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 zenpay.finance · checked Aug 3, 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.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
4 community references
View source14/89 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcezenpay.finance
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
zenpay.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 ↗
zenpay.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.