VirusTotal
19 / 91 engine detections
レポートを開く“TRADE”
The sent-report ledger records the first outgoing report at .
The recorded recipient is complaint@gname.com.
The latest stored availability evidence still shows the domain reachable; 4 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
フィッシング: my1.finance — サーバーエラー (HTTP 503). 証拠の概要: VirusTotal 19/91 (ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar); URLQuery 2 alerts; 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
19 / 91 engine detections
レポートを開く2 threat-system alerts
レポートを開く悪意あり
レポートを開く16 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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | cdn.staticfile.org |
malicious | Sinkholed |
| DNS4EU | my1.finance |
malicious | Sinkholed |
PhishDestroy threat report
Analysis indicates that the domain my1.finance was registered on 14 June 2026 through GNAME.COM PTE. LTD. and resolves to 188.114.97.3, an address owned by Cloudflare (AS13335) located in the United States. The web server returns HTTP 200 and presents a page titled “TRADE”. Automated fingerprinting reveals a stack consisting of PHP, ThinkPHP, Bootstrap, Vue.js, LiveChat, jQuery and Cloudflare services, with the SSL certificate issued by Google Trust Services / WE1. Gridinsoft assigned a trust score of 0/100, and VirusTotal reports 14 of 91 scanners flagging the domain. The site is classified as a crypto drainer, is currently active, and has been blocked by PhishDestroy, MetaMask and SEAL as well as listed on three public blocklists. Nameservers are coen.ns.cloudflare.com and kimora.ns.cloudflare.com. While the classification and infrastructure are confirmed, the specific payload or transaction flow has not been publicly disclosed. Defenders should proactively block the domain and its resolving IP, incorporate the observed technology signatures into detection rules, and monitor DNS and network logs for related activity. Continued surveillance is recommended to track any changes to the infrastructure or threat behavior.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
1JuTSt9C8fRjM8zXVKe4rrAtcVHTQRNR2pFormat validated · Domain analysis3JLvqfvKjLmvQNLykfVpd48twHZEHMrZ5VFormat validated · Domain analysisbc1qea9w34gjlmp43x8enhxjxsme78g4y3tjtw9y0kFormat validated · Domain analysisbc1qmyqjnx4acwapnl5xz03jt772kg36jxtl6z47mtFormat validated · Domain analysis0x667E31942cAdDe19A59d1C53eA4D09a9d63FbD6bFormat validated · Domain analysisTP5gt8ddSpbFJgjXHwNP7nacys81zpHaeBFormat validated · Domain analysisIoC extraction recorded 2026-07-29 01:59:46 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 の評判はこのドメインに起因しません。
coen.ns.cloudflare.comkimora.ns.cloudflare.comLocation describes the IP network.
82b58e6eb4d52d00ff74b2e0288fd90b1d3304ae242a874325f5da4778263d72Saved 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.
transient_503: raw=transient_503; http=503; via=http_proxy; server=cloudflare
my1.finance
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
19/91 engine detections
View source16 community references
View sourcePage captured
View sourcePD-20260618-7E4EE9
No threat flag
View sourcemy1.finance
View sourcePD-20260618-7E4EE9 Recipient: complaint@gname.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
my1.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.