The domain bitgeweb3wallet.cc was observed with a PhishDestroy internal listing on 2026-10-13, serving as a documented entry in the publisher's catalogue. On that same date, a PageSpeed performance score of 65 was also recorded for the domain, offering a technical measurement relevant for context.
Recorded Evidence
VirusTotal checked bitgeweb3wallet.cc on 2026-10-13, recording 0 detections out of 92 total scanners. OTX included the domain in 4 pulses as of 2026-10-13. The domain's registration was documented as occurring on 2026-10-11, and the SSL certificate was issued by Let's Encrypt / YE2. The registrar is listed as Gname.com Pte. Ltd.
Interpretation
PhishDestroy contains a record of bitgeweb3wallet.cc in its internal listing, which documents the domain's inclusion for monitoring within the publisher's own system. VirusTotal provides a measurement of security scanner detections, and its record for this domain contains the results from a large number of security vendors. OTX records show the domain's appearance in multiple intelligence pulses, which are collections of related security observations. These sources together contribute to a multi-faceted technical and security snapshot for the domain as of their respective dates.
Recommended Actions
For any future review of bitgeweb3wallet.cc, preserve the PhishDestroy internal listing and VirusTotal scan records as reference points. Retain the OTX pulse entries for comparison with subsequent intelligence checks. The PageSpeed performance score may also be useful for technical context in later assessments.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 16:00:48 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 16:00:48 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.
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
1 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-13 18:01:17 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
Threat First Observed2026-10-13 16:00:48 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.56.5.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
11 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.
黑名单检测
见于 2 blocklists: MetaMask, SEAL
2026年10月13日
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Brand Impersonation
Impersonation of Bitget
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
2026年10月13日
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月13日
Sent Report Recorded
Stored outgoing record associated with registrar Gname.com Pte. Ltd., 1 abuse contact
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.
