On July 25, 2026 the domain walletweb3.limited was observed as a crypto‑drainer infrastructure that has been taken offline. The site was hosted on Cloudflare’s network (ASN 13335) and resolved to the IP address 172.67.169.219, which is geolocated to the United States. DNS resolution used the Cloudflare‑provided nameservers etienne.ns.cloudflare.com and lady.ns.cloudflare.com, confirming that the registrar was Cloudflare, Inc. No TLS certificate was presented, indicating that the service was delivered over plain HTTP. The only visible page element retrieved during the scan was the HTML title “Welcome | MySite”, which does not reveal the intended victim brand or a specific login flow.
VirusTotal recorded seven detections out of ninety‑five scanned engines, and the domain appears on a single external blocklist. Independent security services have assigned a Gridinsoft trust score of 0 / 100 and PhishDestroy has listed the domain as blocked. The lack of a valid certificate, combined with the low trust score and multiple vendor detections, suggests that the site was likely used to solicit cryptocurrency transfers, fitting the “Crypto Scam” classification supplied in the intelligence.
Because the infrastructure is currently offline, live forensic collection is not possible; however, the recorded IP, nameserver configuration, and detection history provide a reliable fingerprint for future attribution. Defenders should continue to monitor the IP address and associated Cloudflare nameservers for re‑use, add the domain and its IP to internal blocklists, and ensure that any user‑facing applications enforce TLS‑only connections to prevent accidental redirection to similar unencrypted sites. Ongoing watch‑list updates from VirusTotal, PhishDestroy, and other threat‑intel feeds are recommended to capture any resurrection attempts.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='walletweb3.limited', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
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:11:55 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-15 22:15:36 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-15 22:15:36 UTC → 2026-09-30 16:14:55 UTC · 2,561.99hmidpoint estimate ≈ 2026-08-08 07:15:15 UTC · precision very 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.
10 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.
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.
(US)
