This website does not have many visitors We detected cryptocurrency services which can be high risk iQ Abuse Scan has reported this site for spam
According to the SSL check the certificate is valid DNSFilter considers this website safe
証拠の概要
高
VirusTotal
3/91
URLScan
Stored capture
The domain bitgetwallet.capital is currently resolved to the IPv6 address 2606:4700::6812:891, which belongs to AS13335 operated by Cloudflare, Inc. The hosting location is the United States. The domain is delegated to the authoritative nameservers a.share-dns.com and b.share-dns.net. Registration was performed through Gname.com Pte. Ltd., a registrar that frequently appears in abuse reports. The site is listed on a single security blocklist and is explicitly blocked by PhishDestroy, indicating that at least one defensive feed has identified it as malicious. No SSL certificate is present, and the site is reported as offline, meaning no HTTP response is currently reachable. Content analysis is limited to the page title returned by the DNS query, which reads “下载 Bitget Wallet | 适用于iOS、安卓和谷歌浏览器 | Bitget Wallet”.
The title is in Chinese and references a Bitget wallet download for iOS, Android, and Chrome, suggesting a crypto‑related lure. The intelligence tags the domain as a crypto scam that impersonates the Avalanche brand, confirming a brand‑impersonation motive. Detection services provide mixed signals. VirusTotal records two positive detections out of ninety‑five scanners, indicating that a minority of vendors have flagged the domain for malicious behavior. Gridinsoft assigns a trust score of 0 out of 100, and Scamadviser rates the site at 26 out of 100, both reflecting a very low credibility assessment.
The combination of a low trust score, the absence of TLS, and the brand‑impersonation claim strengthens the suspicion of fraudulent activity. Uncertainties remain because the site is offline and no payload, certificate, or network traffic samples are available for deeper forensic analysis. Defenders should therefore treat the domain as high‑risk until further evidence is gathered. Recommended actions include adding bitgetwallet.
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.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bitgetwallet.capital', port=80): Max retries exceeded with url: / (Caused by NewConnection
DOM Analysisanalyzed 2026年5月5日score 10/1009 brand signals
IoC Extractionscanned 2026年7月29日0 wallet · 2 Telegram IoCs
Submitted URLhttp://bitgetwallet.capital/
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-13 01:13:54 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-02 22:16:07 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-02 22:16:07 UTC → 2026-09-30 16:14:55 UTC · 665.98hmidpoint estimate ≈ 2026-09-16 19:15:31 UTC · precision low · 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.
14 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.
(SG)
