This website does not have many visitors We detected cryptocurrency services which can be high risk
According to the SSL check the certificate is valid DNSFilter considers this website safe
証拠の概要
クリティカル
VirusTotal
4/91
OTX
23 community refs
URLScan
Stored capture
The domain bitgetweb3.capital is a cryptocurrency phishing site engaged in brand impersonation targeting Avalanche users. It presents itself as an official Bitget Wallet download portal, offering iOS, Android, and browser extensions, but is designed to deceive victims into exposing wallet credentials or sensitive information. No drainer kit was identified, and the site is currently taken offline, though its prior activity poses a risk to those who interacted with it.
Technical indicators show bitgetweb3.capital had 0 of 95 VirusTotal vendor detections and was not flagged by Google Safe Browsing. It appeared on 1 security blocklist (PhishDestroy) and was registered through UDC (ASN: 140227). The domain resolved to IP address 104.18.8.145, hosted on Cloudflare (AS13335) in the US, with no SSL certificate issued. Nameservers were a.share-dns.com and b.share-dns.net. The observed page title was '下载 Bitget Wallet | 适用于iOS、安卓和谷歌浏览器 | Bitget Wallet', and Gridinsoft assigned a trust score of 0/100.
Victims of bitgetweb3.capital should immediately revoke any token approvals granted to unknown contracts and transfer funds to a new, secure wallet. Change passwords for any accounts accessed on the site and enable two-factor authentication (2FA) where available. Monitor financial statements for unauthorized transactions and report the phishing domain to platforms like Google Safe Browsing, PhishTank, or the impersonated brand’s security team for further action.
Extracted from stored page analysis
Observed indicators
0 wallet · 2 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年5月5日score 88/1008 brand signals
IoC Extractionscanned 2026年7月29日0 wallet · 2 Telegram IoCs
Submitted URLhttps://bitgetweb3.capital/
Favicon Hash
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.
Observed timelinelast reachable: 2026-10-09 22:22:48 UTClast content: 2026-10-09 22:22:48 UTCcurrent episode first observed: 2026-10-10 10:22:09 UTCobserved RIP window: 2026-10-09 22:22:48 UTC → 2026-10-10 10:22:09 UTC · 11.99hmidpoint estimate ≈ 2026-10-10 04:22:28 UTC · precision medium · basis bounded
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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
20 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
