The domain lca.finance has been identified as a credential theft scam, posing a significant threat to users. The domain does not appear to be associated with a specific brand or utilize a particular crypto drainer kit. However, it is actively used in phishing campaigns to steal sensitive information such as login credentials and personal data.
Analysis of the domain reveals the following technical indicators: VirusTotal scores 3/95 for this domain, with a low number of vendors detecting it, which may indicate a relatively new or sophisticated threat. The domain is registered through GNAME.COM PTE. LTD. and resolves to the IP address 185.111.111.156, located in Germany (DE) under the Autonomous System AS212238 Datacamp Limited. The domain was created on May 29, 2026, and is currently listed on three security blocklists: PhishDestroy, MetaMask, and SEAL. The SSL certificate is issued by Let's Encrypt with the serial number YE2, which is common for newly registered domains.
The domain lca.finance remains active, and despite being flagged by a minority of security vendors, the risk level is high due to its involvement in credential theft. Users are advised to avoid interacting with this domain and to implement additional security measures such as multi-factor authentication and regular password changes. Organizations should consider blocking this domain at the network level to prevent unauthorized access and data breaches. Security teams should monitor for any related infrastructure and take appropriate action to mitigate the threat.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Last analyzed Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
Registration & observation details1
Availability observations
Last reachable observation
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='lca.finance', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
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.
