VirusTotal
1 / 91 engine detections
打开报告“BltG0”
冒充 MetaMask: blltgo.top — 内容不可用. 证据摘要: VirusTotal 1/91 (CRDF); URLQuery 2 det.; 2 external blocklist matches (MetaMask, SEAL); CF Radar malicious…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
1 / 91 engine detections
打开报告2 det.
打开报告恶意
打开报告4 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.
PhishDestroy threat report
blltgo.top is an impersonation phishing page that presented itself under the title "BltG0". The zero in place of the letter O is a common lookalike trick meant to pass a quick glance. Because MetaMask and SEAL both listed the domain, its likely targets were crypto users. PhishDestroy first flagged it on 2026-09-25. The site has been offline since 2026-09-26, and its DNS was still inactive on 2026-10-19.
Impersonation pages copy the look and name of a service people already trust, then wait for visitors who arrive from ads, direct messages or mistyped searches. Once the visitor thinks they are on the real site, the page asks for something valuable. That can be a login and 2FA code, a wallet recovery phrase, or a wallet connection that signs away token access. With crypto targets, the loss is usually immediate and irreversible, because whatever the victim hands over is used to empty the account or wallet.
Antivirus coverage was thin. On 2026-09-25, VirusTotal showed 1 detection out of 91 engines, from CRDF. Wallet-focused defenses carried more of the weight: MetaMask's phishing list and the SEAL blocklist both include the domain, alongside PhishDestroy. The domain also appears in 4 AlienVault OTX threat pulses, so several independent researchers tracked it.
The domain was registered through Gname.com Pte. Ltd. on 2026-09-24. PhishDestroy caught it a day later, and it went dark the day after that. A lifespan of roughly 48 hours fits a disposable domain meant to be burned quickly. It was hosted on SonderCloud Limited's network in the US at 206.119.172.49, and it served a TLS certificate so the page would show a padlock like a legitimate site.
If you typed a password or 2FA code into this page, change that password everywhere you reused it, reset 2FA, and review recent account activity. If you entered a seed phrase or private key, treat the wallet as compromised and move any remaining funds to a newly created wallet. If you connected a wallet and signed anything, revoke token approvals with a reputable approval checker. Defenders should block the domain and its IP, search logs for visits around 2026-09-24 to 2026-09-26, and watch for new lookalike domains using the "BltG0" naming.
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.
a.share-dns.coma1.share-dns.comb.share-dns.netb1.share-dns.netLocation describes the IP network.
Saved 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.
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
可访问→不可用
0→1
可访问
4 community references
View sourceNo threat flag
View source1/91 engine detections
View sourcePD-20260925-CAD7EE
Page captured
View sourceblltgo.top
View source已存储 79 个仿冒域名
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
blltgo.top
PD-20260925-CAD7EE Recipient: abuse@cogentco.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 ↗
blltgo.top)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.