跳转到安全报告
域安全和威胁情报
dai56789.top favicon

dai56789.top

“BltG0”

注册商
Gname
Resolved IP
206.119.182.8
Registered
2026年9月26日
PhishDestroy assessment 关键
可用性 最后已知的活跃状态 最新存储的可达性观察 观察到 · HTTP probe
病毒检测总数:16/92 存储的阻止列表匹配项:2 自动品牌标签:MetaMask 年轻域名:24 天龄 Google Safe Browsing: threat flag recorded
OTX: 1 ref 2026年9月29日 1 Report Sent
API
该域名已被标记为恶意域名
安全引擎报告检测:16。 报告匹配的公共黑名单:2。 请格外小心——不要输入凭据或个人信息。
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@cogentco.com. The latest stored availability evidence still shows the domain reachable; 21 days 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.

Elapsed since first report
21 days
Reports sent
1
Latest case ID
PD-20260929-86ECDF
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
报告概览

冒充 MetaMask: dai56789.top — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 16/92 (alphaMountain.ai, BitDefender, CRDF, Emsisoft, Forcepoint ThreatSeeker); URLQuery 2…

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

Source evidenceVirusTotal 16 / 92 · Google Safe Browsing: flagged · OTX 1 references 6 sources

VirusTotal

16 / 92 engine detections

打开报告

Google Safe Browsing

Threat flag recorded

打开报告

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

Analysis

关键
VirusTotal
16 / 92
OTX
1 community ref
Page captures
3

PhishDestroy threat report

Overview

dai56789.top is an impersonation phishing page that poses as a legitimate service to trick crypto users into handing over access to their accounts or wallets. PhishDestroy first detected it on 2026-09-29, only three days after the domain was registered. As of 2026-10-19 the site was still online and serving its phishing content, so it remains a live risk.

How the scam works

Impersonation pages copy the look of a trusted brand or service and persuade visitors that they are on the real site. The victim is then asked to log in, enter a recovery phrase or private key, or connect a wallet and approve a request. Whatever the victim enters or signs goes straight to the operators, who can then empty the account or wallet. The browser tab shows only the random string "BltG0" rather than a brand name, while we classify the page as impersonation phishing.

Evidence

On 2026-10-07, 16 of 92 VirusTotal engines flagged the domain, including alphaMountain.ai, BitDefender, CRDF, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data and Google Safe Browsing. Google Safe Browsing classifies it as SOCIAL_ENGINEERING, so Chrome, Firefox and Safari users should see a red warning before the page loads. The domain also appears on the MetaMask and SEAL blocklists alongside PhishDestroy, which means wallet users are warned at the point of connection. One AlienVault OTX threat pulse references it as well.

Infrastructure

The domain was registered through Gname.com Pte. Ltd. on 2026-09-26 and was already phishing when we caught it three days later. That short gap fits a disposable domain set up for a quick campaign. The numbered .top name looks like one entry in a series of similar domains. The site is hosted on SonderCloud Limited's network in the US at 206.119.182.8.

What to do

Do not enter anything on dai56789.top. If you typed a password there, change it on the genuine service and turn on two-factor authentication. If you entered a recovery phrase or private key, treat that wallet as compromised and move any remaining funds to a new wallet created on a clean device. If you connected a wallet and approved a request, revoke those token approvals with a reputable approval checker. Security teams should block the domain and its IP at DNS and proxy level and search logs for visits since 2026-09-26.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask 已列入 View source
PhishDestroy PhishDestroy list View source
SEAL 已列入 View source

Last checked

已保存的截图 · 3 captures

Observed page title
BltG0
TLS 证书
颁发者 Let's Encrypt / YR1 · stored validity ends in 65 days

Domain details

域名
URLScan verdict 分析完成 score 0 report ↗
Google Safe Browsing 已标记 Social engineering checked 2026年10月13日
IP 信誉 abuse score 0/100 0 reports checked 2026年9月29日
OTX tags blocklistcryptodrainerfraudphishdestroyphishingscam
注册商 Gname CN(CN)
滥用举报联系方式abuse@cogentco.com, complaint@gname.com
ICANN 注册管理机构ICANN Lookup (RDAP) →
注册信息创建 2026年9月26日 (24d · Very New!) — Expires 2027年9月26日
HTTP 状态码200
技术详情Provenance & timestamps
首次发现2026年9月29日
DOM Analysisanalyzed 2026年10月9日score 100/100
Submitted URLhttp://dai56789.top/
Favicon Hash
案件 ID
ICANN OVERSIGHT

认证和 RAA 背景

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft 不会自动发送任何内容。

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
206.119.182.8
Network ASN
AS133199
Organization
Solustack Limited
Observed location
Los Angeles, US
Server header
nginx

域名服务器 4

  • a.share-dns.com
  • a10.share-dns.com
  • b.share-dns.net
  • b10.share-dns.net

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / YR1
Valid from
2026-09-26 00:03:25
Valid until
2026-12-25 00:03:24
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-29 07:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint8a6f2ec6cd07f0d9f4e542063ab1357e34e063bb10a73f7b99301c79c9cf6e21
Certificate names · 3 SANs
  • dai567.top
  • www.dai567.top
  • www.dai56789.top

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

Latest Classified Outcome 2026-10-19 22:28:59 UTC

Primary outcome 内容在线 reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation 内容在线 Ordinary HTTP content served 90% 2026-10-19 22:28:59 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-19 22:35:31 UTC last content: 2026-10-19 22:28:59 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.dai56789.topDomain record

The original observation time is not recorded for these hostnames.

技术 · 8 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

16 / 92 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 6 detections
alphaMountain.ai
BitDefender
CRDF
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
卡巴斯基
LevelBlue
Lionic
Netcraft
SOCRadar
Sophos
Webroot

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Stored observation history21

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

    未知→live_content

    content_served

  2. Availability monitor · Recorded state

    未知→live_content

    content_served

  3. Availability monitor · Recorded state

    未知→live_content

    content_served

  4. Availability monitor · Recorded state

    未知→live_content

    content_served

  5. Availability monitor · Recorded state

    未知→live_content

    content_served

Earlier observations 16
  1. Availability monitor · Recorded state

    未知→live_content

    content_served

  2. Availability monitor · Recorded state

    未知→live_content

    content_served

  3. Availability monitor · Recorded state

    未知→live_content

    content_served

  4. Availability monitor · Recorded state

    未知→live_content

    content_served

  5. Availability monitor · Recorded state

    未知→live_content

    content_served

  6. Availability monitor · Recorded state

    未知→live_content

    content_served

  7. Availability monitor · Recorded state

    未知→live_content

    content_served

  8. Availability monitor · Recorded state

    未知→live_content

    content_served

  9. Availability monitor · Recorded state

    未知→live_content

    content_served

  10. Availability monitor · Recorded state

    未知→live_content

    content_served

  11. Availability monitor · Recorded state

    未知→live_content

    content_served

  12. Availability monitor · Recorded state

    未知→live_content

    content_served

  13. Availability monitor · Recorded state

    未知→live_content

    content_served

  14. Availability monitor · Recorded state

    未知→live_content

    content_served

  15. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  16. Availability monitor · First collection record

    可访问

Recorded activity

6 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    16/92 engine detections

    View source
  3. Abuse report sent

    PD-20260929-86ECDF

    abuse@cogentco.com
  4. URLScan

    Page captured

    View source
  5. AlienVault OTX

    1 community references

    View source
  6. Added to PhishDestroy

    dai56789.top

    View source

仿冒域名

已存储 79 个仿冒域名

显示全部(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.

dai56789.top

证据与外部报告

已提交证据快照
Sent: Ledger records: 1 Case ID: PD-20260929-86ECDF Recipient: abuse@cogentco.com
Page title stored with report: BltG0
PDF notice generated Notice text archived (317 chars)
Abuse notice text as sent to the provider
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)
深度分析
Help & reporting

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

6 evidence signal groups linked 1 stored notification records 最后已知的活跃状态
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

Official reporting routes

警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

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

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.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 dai56789.top)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

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

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

  • 联邦调查局(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

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

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

实时威胁动态 对该列表提出异议
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

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

embed.html
<iframe
  src="https://phishdestroy.io/zh/embed/domain/dai56789.top"
  title="PhishDestroy threat report for dai56789.top"
  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>