VirusTotal
7 / 89 engine detections
レポートを開く“Service Status”
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; 1 month 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.
MetaMaskなりすまし: io-eng.icu — 未検証. 証拠の概要: VirusTotal 7/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); Spamhaus DBL_PHISH; 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 89 engine detections
レポートを開く15/100
レポートを開くDBL_PHISH
checked — no detections recorded
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く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
io-eng.icu is an impersonation phishing page dressed up as a "Service Status" site, and it sits on the MetaMask and SEAL blocklists, which track threats to crypto wallet users. PhishDestroy first caught it on 2026-09-14. As of 2026-10-19 the domain still responded, but its DNS was no longer serving the phishing content.
The page title "Service Status" is generic and names no brand, while we classified the site as impersonation phishing. Fake status pages typically claim there is an outage, a pending migration or an account problem, then push the visitor to "verify" or "reconnect." That step is where the theft happens. Victims are asked for login credentials, a wallet recovery phrase, or a wallet connection that grants the attacker control. Anyone who completes it can lose account access or the crypto held in the affected wallet.
Seven of 89 VirusTotal engines flagged the domain in a 2026-09-24 scan: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar and VIPRE. That is a modest share, but it is backed by stronger signals. Spamhaus lists the domain in its DBL under the phishing category, and MetaMask and SEAL both blocklist it alongside PhishDestroy. Four AlienVault OTX threat pulses also reference it, so other researchers have tied it to malicious activity.
The domain was registered on 2026-09-12 through Gname.com Pte. Ltd., just two days before PhishDestroy detected it. That short gap is typical of throwaway domains launched for a quick campaign. The cheap .icu extension and a name built to look like a generic engineering or service subdomain fit the same pattern. Traffic runs through Cloudflare, Inc. on an address geolocated to Canada, which hides the real origin server.
If you entered a recovery phrase on io-eng.icu, treat that wallet as compromised and move any remaining funds to a new wallet created with a fresh phrase. If you connected a wallet or signed anything, revoke the token approvals granted during that visit. If you typed a password, change it everywhere you reused it and turn on app-based two-factor authentication. Security teams should block the domain at DNS and the proxy, and search logs for any visits since 2026-09-12.
Last checked
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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 の評判はこのドメインに起因しません。
david.ns.cloudflare.comelinore.ns.cloudflare.comLocation describes the IP network.
070a94fbb91c1f9d681452f04dde2dc3c1fe7491cef76a6368cea6b06ba542b3Saved 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 io-eng.icu · checked Sep 14, 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.
io-eng.icu
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
live_content→dns_inactive
dns_nxdomain
不明→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→redirected
http_redirect
不明→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
2→3
到達可能
4 community references
View sourceNo threat flag
View source7/89 engine detections
View sourcePD-20260914-819986
io-eng.icu
View sourcePage captured
View source保存された類似ドメイン:79 件
PD-20260914-819986 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 ↗
io-eng.icu)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.