This domain, liberascudorio.digital, was registered on March 6, 2026, through Name.com, Inc., and is flagged as a brand impersonation threat targeting Bitcoin. Analysis indicates the domain resolved to IP 104.21.3.65, hosted on Cloudflare's network (AS13335), a common infrastructure choice for malicious actors due to its privacy and proxy services. The domain was taken offline by July 24, 2026, but prior to its removal, it was detected by 8 of 94 security vendors on VirusTotal and appeared on three security blocklists, including PhishDestroy, MetaMask, and SEAL. The page title, 'Libera Scudorio 2026: Approfitta delle opportunità Bitcoin ETF,' suggests the scam promoted fraudulent Bitcoin ETF opportunities, likely leveraging social engineering tactics to deceive victims.
No SSL certificate was present, which is unusual for legitimate financial or investment platforms and further supports the assessment of malicious intent. Infrastructure analysis reveals the domain used Cloudflare nameservers (jule.ns.cloudflare.com, felipe.ns.cloudflare.com), which can obscure the true hosting origin. The absence of an SSL certificate and the use of a generic hosting provider align with typical phishing domain characteristics. While the domain is currently offline, defenders should treat any residual DNS records or cached content as high-risk.
Organizations are advised to block the domain and its associated IP (104.21.3.65) at the network level, monitor for related domains using similar naming conventions (e.g., 'libera,' 'scudorio,' or 'ETF' keywords), and alert users to the Bitcoin ETF scam theme. If logs indicate prior access, initiate incident response procedures to assess potential exposure or credential compromise. Given the elevated risk level and prior detection by multiple security vendors, this domain should be considered malicious until further evidence suggests otherwise.
DOM Analysisanalyzed 2026年7月29日score 70/1007 brand signals
Submitted URLhttp://liberascudorio.digital/
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:08:53 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-03-23 22:18:31 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-03-23 22:18:31 UTC → 2026-09-30 16:14:55 UTC · 4,577.94hmidpoint estimate ≈ 2026-06-27 07:16:43 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.
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)
