Is lc-collab.land a scam? TrustSniffer's high-risk assessment: 0/100

Security Alert

Fortinet, Kaspersky, Sophos flagged this site in external intelligence checks, indicating elevated compromise/scam exposure that requires immediate caution.

lc-collab.land is a newly registered website on the ".land" top-level domain, fronted by a major content-delivery network. Analysis of its homepage found no identifiable products, services, branding or business model, so its purpose cannot be established from the site itself. What it does present to a visitor is a page that loads external resources heavily and runs an inline script that the behavioral analysis flagged as suspicious.

Scam/Impersonation Risk

Contradictory signals are present, and they are decisive. Several tier-one security vendors currently flag the domain as malicious, and a further group of engines marks it suspicious. This amounts to a confirmed blacklist-level external detection. The site has no countervailing reputation: it has no established traffic ranking and no recognition as a known brand or platform. Its registration is only a few months old, which is typical of disposable or campaign-style infrastructure. The behavioral analysis adds corroboration. Nearly all of the homepage's activity is directed at third-party hosts, a suspicious inline script was observed, and the page issued several outbound POST requests. None of those requests went to hosts outside the known-benign set, and no wallet-drainer, clipboard-hijack, hidden-form or credential-forwarding behavior was seen. The malicious classifications therefore rest chiefly on external vendor detections, not on a demonstrated exploit in the sandbox. No conflicting legal identities and no specific brand impersonation were observed. The elevated assessment comes from the vendor detections, the very recent registration and the page's behavior, not from an identified impersonation target. Evidence:

• Homepage and domain reputation: 11 security engines classify the domain as malicious and 2 as suspicious, including three tier-one vendors.
• Domain registration: created 2026-08-15 (~0.2 years old), which makes it a very young domain.
• Homepage behavior: about 97% of observed activity was external, with 3 external POST requests and 1 suspicious inline script across 3 sandbox runs.
• Homepage behavior: no wallet-connection, clipboard-write, hidden-form or external password-form activity was recorded.

Regulatory Verification Notes

No legal, terms, privacy or about content could be assessed. The site therefore offers no named operating entity, licence or registration number to evaluate. Registrant details are incomplete and the registration is privacy-limited, which is ownership opacity and an administrative limitation, not an identity contradiction. No third-party regulatory or broker listing exists for the domain, so there is no external confirmation of any regulated status. The technical hygiene is ordinary and does not offset the reputational findings: the transport encryption is valid, and the site is served from a recognised network. Evidence:

• Domain registration: registered through NICENIC International Group Co., Limited, with registrant details incomplete; registration runs to 2027-08-15.
• Transport encryption: a domain-validated TLS certificate issued by WE1, valid to 2027-01-11 (76 days remaining at analysis). Domain validation confirms only control of the domain, not the operator's identity.
• Hosting: served from AS13335 (Cloudflare, Inc., US).
• Third-party broker coverage: no matching entry was found.

What to Verify Next

Verification here concerns whether the external detections can be cleared. It does not concern establishing credibility. The domain's origin and the entity behind it should be established through an independent channel before any engagement, for example by confirming the address through an official, offline route from the organization it claims to represent. If the site was reached through a message, advertisement or social-media link, the sender and the originating channel should be authenticated separately. Anyone who has already interacted with the domain should treat that session as potentially exposed and review any accounts or devices involved. Any official support or contact channels should be confirmed independently of this site. Evidence:

• Domain registration: the very recent creation date means no long operating history can be relied on.
• Homepage reputation: the malicious classifications from multiple tier-one vendors remain active and unresolved.
• Registrant data: the registrant is incomplete, so ownership cannot be confirmed from the registration record.

Summary Verdict

The overall posture is clearly adverse. Active external threat detections from multiple leading vendors, together with a very recently created domain and unexplained third-party-heavy page behavior, produce a high-risk assessment that technical hygiene cannot offset. No credible, verifiable legitimacy signal exists to counterbalance this, and the real-world operator remains unidentified.

Infrastructure Integrity

The site is served entirely through Cloudflare's CDN and web-application firewall. Every observed address is a Cloudflare edge address in the United States, and no origin server could be observed. Cloudflare is a reputable provider, and the valid transport encryption is a minor mitigating factor. However, this infrastructure is available to anyone, so it says nothing about the operator's legitimacy. Edge-only visibility also prevents independent verification of the true hosting location and allows content to be swapped quickly without any visible infrastructure change. The infrastructure does not offset the active threat detections.

Closing Assessment

The domain should be treated as unsafe for any sensitive interaction. Account login, credential entry, wallet connection and any payment or financial transaction should be avoided. Viewing the page at all should be limited to an isolated, non-production environment. Links to this domain received from unsolicited messages should not be followed, and the domain should be reported to the internal security team and blocked until the external detections are cleared.