VirusTotal
3 / 91 engine detections
レポートを開く“Default page”
認証情報フィッシング: io-chip.online — コンテンツが利用できません. 証拠の概要: VirusTotal 3/91 (alphaMountain.ai, Gridinsoft, SOCRadar); 2 external blocklist matches (MetaMask, SEAL)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 91 engine detections
レポートを開くchecked — no detections recorded
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開く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
This domain, io-chip.online, is currently under investigation for potential credential harvesting activity. Credential harvesting sites mimic legitimate login pages to trick users into entering sensitive information such as usernames, passwords, or financial details. These stolen credentials are often used for unauthorized account access, identity theft, or financial fraud. While the site may appear harmless or inactive at first glance, its infrastructure and registration patterns align with known phishing operations targeting unsuspecting users. Analysis indicates the domain was registered on June 25, 2026, through HOSTINGER operations, UAB, a registrar frequently used by threat actors to deploy phishing infrastructure. As of the latest scan, VirusTotal reports 0 detections out of 95 security engines, suggesting the site has not yet been widely flagged or may employ evasion techniques. The domain resolves to the IP address 145.79.20.71 and uses a Let's Encrypt SSL certificate, which is commonly abused to lend a false sense of legitimacy. The page title, 'Default page,' further suggests the site may be in a preparatory or transitional phase, awaiting deployment of malicious content. If you have visited io-chip.online or entered any information on the site, immediate action is required. First, change passwords for any accounts that may have been exposed, prioritizing email, banking, and other high-value services. Enable multi-factor authentication (MFA) where available to add an additional layer of security. Monitor accounts for unusual activity, such as unauthorized logins or transactions, and report any suspicious behavior to the relevant service providers. Additionally, consider running a full scan of your device using updated security tools to detect potential malware or backdoors. Users should also report the domain to their organization's security team or to platforms like Google Safe Browsing or PhishTank to help prevent further exploitation.
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.
byte.dns-parking.compixel.dns-parking.comLocation describes the IP network.
Google PageSpeed Insights — mobile performance audit of io-chip.online · checked Jun 27, 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='io-chip.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
io-chip.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
3/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcePD-20260627-27B5BA
io-chip.online
View sourcePD-20260627-27B5BA Recipient: abuse@hostinger.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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-chip.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.