This website does not have many visitors We found many low rated websites on the same server We could not analyze the content of the site
According to the SSL check the certificate is valid DNSFilter considers this website safe
증거 요약
심각
VirusTotal
11/89
OTX
26 community refs
URLScan
Stored capture
The domain bitgetwalletweb30.capital, a phishing site impersonating the Avalanche brand, is no longer active and appears to have been taken down. This domain was designed to deceive users into believing it was a legitimate Avalanche-related service.
Six out of 95 security vendors detected bitgetwalletweb30.capital as malicious. Among these, Fortinet, Sophos, Forcepoint ThreatSeeker, and alphaMountain.ai specifically flagged the domain. It was listed on one public blocklist, though Google Safe Browsing did not flag it as unsafe.
Infrastructure analysis shows the domain was registered with UDC, operating under ASN 140227, and resolved to the hosting IP address 104.18.8.145. This domain was first seen on 2025-11-04.
Block bitgetwalletweb30.capital at the network perimeter and flag 104.18.8.145 as a confirmed indicator of compromise.
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.
등록 정보생성됨 2025년 10월 24일 (354d)—Expires 2026년 10월 24일
HTTP 상태301 Moved Permanently
기술 세부 정보Provenance & timestamps
최초 발견2025년 11월 4일
DOM Analysisanalyzed 2026년 5월 5일score 100/1008 brand signals
IoC Extractionscanned 2026년 7월 29일0 wallet · 2 Telegram IoCs
Submitted URLhttps://bitgetwalletweb30.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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 10:20:58 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-13 10:20:58 UTClast content: 2026-10-11 10:21:11 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.
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.
16 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
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
How we investigate & report
Public scans, evidence and abuse channels
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.
