跳转到安全报告
分析仪表盘
域安全和威胁情报
io-sign.com favicon

io-sign.com

“Suspected Phishing | Cloudflare”

注册商
Global Domain Group
Resolved IP
188.114.97.9
PhishDestroy assessment 关键
可用性 可达 · 访问受限 可达响应；页面内容未经验证 观察到 · HTTP probe
风险信号
病毒检测总数：6/89 存储的阻止列表匹配项：2 自动品牌标签：MetaMask 最后已知的活跃状态
OTX: 3 refs 2026年8月31日 CDN
API
该域名已被标记为恶意域名
安全引擎报告检测：6。 报告匹配的公共黑名单：2。 请格外小心——不要输入凭据或个人信息。
VirusTotal
6 / 89
engine detections
Google Safe Browsing
No threat flag
OTX
3
community references
Page captures
1
open gallery
报告概览

冒充 MetaMask: io-sign.com — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 6/89 (alphaMountain.ai, Chong Lua Dao, CRDF, Forcepoint ThreatSeeker, Gridinsoft); 2…

为保留原始取证记录，下方的 PhishDestroy AI 详细分析仍使用英文。

Source evidenceVirusTotal 6 / 89 · OTX 3 references 6 sources

VirusTotal

6 / 89 engine detections

打开报告

Google Safe Browsing

No threat flag

打开报告

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

关键
VirusTotal
6 / 89
OTX
3 community refs
Page captures
1
Page captures Source results Registration record

PhishDestroy threat report

Overview

io-sign.com is an impersonation phishing site. The name points at a signing step, and its listing by MetaMask and SEAL indicates it targeted cryptocurrency wallet users. PhishDestroy first flagged it on 2026-08-31. The site went offline on 2026-09-13 and was still dead, with its content blocked by the provider, at the last check on 2026-10-19.

How the scam works

Impersonation pages copy a trusted service's look closely enough that visitors act without double-checking the address. Crypto-focused versions usually ask the visitor to connect a wallet and approve a signature or transaction framed as verification, a login or a routine "sign" step. That approval can hand an attacker control over tokens, or the page may ask for a seed phrase outright. The last page title we captured was "Suspected Phishing | Cloudflare", which is Cloudflare's own warning screen rather than the impersonated content, while our classification is impersonation phishing.

Evidence

On 2026-09-12, 6 of 89 VirusTotal engines flagged the domain: alphaMountain.ai, Chong Lua Dao, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That count is modest, but these vendors work independently, and the domain also appears on the MetaMask and SEAL blocklists alongside PhishDestroy. Wallet-side blocking matters most for this threat because it warns users at the point where they would connect. Three AlienVault OTX pulses also reference the domain.

Infrastructure

The domain was registered through Global Domain Group LLC and sat behind Cloudflare's network on an address geolocated to Canada. That means the real origin server was hidden from view. The provider's phishing interstitial and the later provider block show the takedown came at the network edge. The Google Trust Services certificate is the kind issued automatically to Cloudflare-fronted sites, so the padlock said nothing about who ran it. The site lasted about two weeks between our first detection and going offline.

What to do

If you connected a wallet to io-sign.com, review and revoke any token approvals or permissions granted around that time with a reputable approval checker. Move remaining funds to a fresh wallet if you signed anything you did not understand. If you typed a seed phrase into the site, treat that wallet as compromised and transfer everything to a new one created with a new phrase. Defenders should block the domain at DNS and proxy level and search logs for visits from late August through mid-September 2026.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask 已列入 View source
PhishDestroy PhishDestroy list View source
SEAL 已列入 View source

Last checked

已保存的截图 · 1 capture

Primary capture 1 / 1
来源Primary capture
Recorded2026-08-31 18:29 UTC
StateStored capture
Position1 / 1
Open capture Wayback 下载

Domain details

域名
URLScan verdict 分析完成 score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX tags 2026-08activeall-domainsblocklistcontentcrypto域名drainerfraudmonthlyphishdestroyphishingscam
注册商 Global Domain Group US(US)
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询io-sign.com 的 ICANN RDAP →
HTTP 状态码403 Forbidden
Elapsed Since First Report 13 days
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 可达 · 访问受限.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据，例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2026年8月31日
Favicon Hash
Observed page title
Suspected Phishing | Cloudflare
Automated brand references
MetaMask
TLS 证书
颁发者 Google Trust Services / WE1 · stored validity ends in 38 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.9
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP 声誉不属于此域。

域名服务器 1

  • natasha.ns.cloudflare.com

Location describes the IP network.

TLS 证书

Issuer
Google Trust Services / WE1
Valid from
2026-08-30 00:16:22
Valid until
2026-11-28 01:14:05
Validity
Within stored validity dates
Collection time
2026-09-11 01:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprintfa0839e546697273cd9dc5186a7c5b615f2d93bc6dcd48df50567723f83f5d6f

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 188.114.97.9rapiddns.io
技术 · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

6 / 89 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
Chong Lua Dao
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history12

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  5. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

Earlier observations 7
  1. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  5. Availability monitor · Recorded state

    不可用→可访问

  6. Availability monitor · Recorded state

    可访问→不可用

  7. Availability monitor · First collection record

    可访问

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    6/89 engine detections

    View source
  3. AlienVault OTX

    3 community references

    View source
  4. Added to PhishDestroy

    io-sign.com

    View source

仿冒域名

已存储 79 个仿冒域名

etamask.io omission 内部报告 meetamask.io repetition 内部报告 megamask.io replacement 内部报告 metam.ask.io subdomain 内部报告 metamaak.io replacement 内部报告 metamadk.io replacement 内部报告 metamaks.io transposition 内部报告 metamassk.io insertion 内部报告 metamsask.io insertion 内部报告 metamssk.io replacement 内部报告 metanask.io homoglyph 内部报告 metanmask.io homoglyph 内部报告
显示全部（67）
metasmask.io insertion 内部报告 metramask.io insertion 内部报告 mewtamask.io insertion 内部报告 mmetamask.io homoglyph 内部报告 mtamask.io omission 内部报告 mwetamask.io insertion 内部报告 nmetamask.io homoglyph 内部报告 metamark.io bitsquatting 内部报告 metamaskj.io addition 内部报告 metammask.io homoglyph 内部报告 metamnask.io homoglyph 内部报告 emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

io-sign.com

证据与外部报告

证券分析
URLScan Analyzed VirusTotal 6 det. ChainPatrol URLQuery Scamadviser 80 trust SSL 实验室 CF雷达 打开报告 OTX 3 refs WOT 黑名单检查器 URLVoid Sucuri SiteCheck MDN 观测站
OSINT与情报分析
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox 哈德逊岩 Sign-in search IntelX crt.sh 证书 WHOIS Wayback
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析
Help & reporting

您是否受到本网站的影响？

5 evidence signal groups linked 0 stored notification records 可达 · 访问受限

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息，或者从此域下载了文件，请立即采取措施。以下资源可帮助您报告事件并保护自己。

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review 不是执法报告
域名申诉
如果您拥有该域名并认为该列表不正确，请请求审核
警惕“数据恢复”诈骗！ 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident

针对受害者的建议与指导

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.

  • 更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息？

联邦调查局（FBI）指南

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的（包括 io-sign.com)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整，对调查仍有帮助。

我应该向哪里举报这起诈骗？

  • 联邦调查局（FBI）IC3 — 互联网犯罪投诉中心（美国联邦举报渠道）
  • 欧洲刑警组织 — 欧洲网络犯罪报告（欧盟）
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 当地警方 — 即使无法立即采取行动，也能留下正式记录

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站，使得欺诈行为更难被察觉

将来我该如何保护自己？

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前，请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

检查任意域名

使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析

立即扫描

举报网络钓鱼

将可疑域名提交至我们的威胁数据库——保护社区

报告

实时威胁动态

最近的网络钓鱼报告和观察到的可用性变化

监控

随时掌握最新信息，确保安全

请实时监控威胁，或者如果您认为这是误报，请对该条目提出异议

实时威胁动态 对该列表提出异议
About this reportSources, observation dates and corrections

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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/io-sign.com"
  title="PhishDestroy threat report for io-sign.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>