The domain walletconnect.limited was observed as offline at the time of analysis on July 24, 2026. Registration was performed through Cloudflare, Inc., and the authoritative nameservers are etienne.ns.cloudflare.com and lady.ns.cloudflare.com. DNS resolution points to the IP address 172.67.206.93, which belongs to AS13335 Cloudflare, Inc. and is geolocated in the United States. No TLS certificate was presented, indicating that the site was served without encryption. The only visible page title returned by the HTTP endpoint is “Welcome | MySite,” which does not directly reference the targeted brand.
Gridinsoft’s trust scoring system assigned a score of 0 out of 100, reflecting an extremely low confidence rating. VirusTotal analysis shows that 11 of 95 security‑vendor engines flagged the domain, suggesting a measurable level of malicious activity. The domain appears on a single external blocklist and has been explicitly blocked by the PhishDestroy service. Intelligence categorises the activity as a crypto‑related scam that impersonates WalletConnect, the legitimate brand targeted in the campaign. The combination of Cloudflare‑based hosting, lack of SSL, low trust score, and multiple vendor detections aligns with typical infrastructure used for brand‑impersonation scams.
However, the exact content hosted on the site, including any credential‑harvesting forms or payload delivery mechanisms, remains unknown because the page was not fully captured. Defenders should add walletconnect.limited to DNS‑based blocklists, enforce outbound filtering for the associated IP address, and monitor Cloudflare‑associated ASN traffic for related anomalies. Users of the WalletConnect ecosystem should be warned that any unsolicited communication referencing the brand and directing to this domain is unauthorised.
DOM Analysisanalyzed 2026年4月23日score 78/1001 brand signal
Submitted URLhttp://walletconnect.limited/
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-19 01:10:27 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-05-16 21:51:35 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-16 21:51:35 UTC → 2026-09-30 16:14:55 UTC · 3,282.39hmidpoint estimate ≈ 2026-07-24 07:03: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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='walletconnect.limited', port=80): Max retries exceeded with url: / (Caused by NewConnectio
walletconnect.limited
保存済みの結果
到達不能
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(US)
