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
保存されたブロックリスト、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.