Analysis of lombard-lux.finance as of July 24, 2026 indicates that the domain is currently offline but was previously used as a crypto‑drainer targeting MetaMask users. The site resolved to the Cloudflare edge address 104.21.32.1, hosted in the United States under ASN 13335 (Cloudflare, Inc.). Its authoritative nameservers, ignacio.ns.cloudflare.com and miki.ns.cloudflare.com, confirm that the infrastructure relied on Cloudflare’s DNS service. Registration was handled by Web Commerce Communications Limited, a registrar commonly associated with bulk‑registered domains.
No TLS certificate was served, meaning the site operated without HTTPS encryption. The page title observed during the brief capture was “Kaito,” and the campaign employed the Angel Drainer kit, a known tool for siphoning cryptocurrency assets. VirusTotal records show that ten of ninety‑five scanning engines flagged the domain as malicious, and the domain appears on two public blocklists, specifically PhishDestroy and ScamSniffer. Gridinsoft assigned a trust score of zero out of one hundred, reinforcing the malicious assessment.
The domain explicitly impersonated the MetaMask brand, aligning with the reported fake‑airdrop scam type. While the domain is now taken offline, defenders should continue to monitor the associated IP address and Cloudflare nameservers for reuse, add the domain and its IP to internal blocklists, and enforce strict URL filtering for any requests to lombard‑lux.finance. Network traffic to the resolved IP should be inspected for signs of the Angel Drainer payload, and endpoint protection should be updated to recognize the identified indicators of compromise. Because the site lacked HTTPS, any credential capture would have occurred over cleartext, further emphasizing the need for robust user education on verifying TLS connections when interacting with MetaMask‑related services.
DOM Analysisanalyzed 2026年4月24日score 25/1001 brand signal
Submitted URLhttp://lombard-lux.finance/
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:13:27 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-08-11 22:13:41 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-11 22:13:41 UTC → 2026-09-30 16:14:55 UTC · 1,194.02hmidpoint estimate ≈ 2026-09-05 19:14:18 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.
Last analyzed Previous stored snapshot: 13 detections
ADMINUSLabs
ChainPatrol
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
ソフォス
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
1194.02
Estimate basis
Bounded by observations
Estimate precision
very_low
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='lombard-lux.finance', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
lombard-lux.finance
保存済みの結果
到達不能
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
あなたの仮想通貨取引所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
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.
(MY)
