Is crypto-l9k.netlify.app safe? TrustSniffer's low-trust assessment: 25/100

Overview

This website is a subdomain on a shared application-hosting platform (Netlify) whose root page currently returns the platform's generic "Site not found" 404 response. The page contains no products, pricing, company identity, contact details or legal text. The subdomain label suggests a crypto theme, but the visible page offers no service, so no business model can be identified from it.

Scam/Impersonation Risk

The assessment is cautionary because of a confirmed contradiction. The domain is blacklisted by external reputation sources, with one detection rated malicious and another suspicious. The behaviour observed in the page does not match its visible content. The homepage presents a bare error message, yet repeated automated sessions found concealed forms in every run, including password-type fields, and the page changed heavily after interaction. This points to markup that is not visible to a casual visitor and that can be activated or swapped in later. A hosted-subdomain 404 is also a common state for a throwaway or staging deployment before content is switched on. The domain name closely resembles the hosting platform's own domain, and the page analysis flagged this as a suspected brand lookalike, although no confirmed impersonation was recorded. Network behaviour shows rapidly rotating, ephemeral addressing, but no wallet-connection, clipboard-hijack or drainer activity was observed. The site's owner cannot be identified, so intent cannot be established, but the combination of a blacklist hit, concealed credential-style forms and an empty front page is a meaningful risk pattern. Evidence:

• Homepage: renders only the hosting platform's 404 notice (about 370 characters of text) and carries no title, description or business content.
• Automated sandbox, three of three runs: concealed forms were present on each run, with password-type fields, while no login form was visible.
• Automated sandbox: more than 4,000 page changes were recorded after interaction, which is very high for a static error page.
• Domain provenance: registered about 23 days ago (~0.06 years); the web archive holds 1 snapshot, in 2026, covering 1 year tracked.

Regulatory Verification Notes

No licence, registration number, company name, jurisdiction or governance information appears anywhere on the site. The only reachable page is a platform error notice, so there are no legal or identity pages to assess. A missing licence is a verification gap and not evidence of wrongdoing in itself. Here it cannot be weighed on its own, because the site presents no regulated activity to license and the real-world operator cannot be linked to the domain. The domain is very new, and the ownership record is incomplete. No broker-reputation entry matches the site, and nothing suggests third-party regulatory coverage. Ownership therefore remains unattributed, and no legitimacy can be inferred from the infrastructure alone. Evidence:

• Homepage: contains no company name, licence claim, terms, privacy policy or contact page.
• Domain registration: created roughly 23 days ago, with an incomplete owner record.
• Hosting: served from AS16509 (AMAZON-02, Amazon.com, Inc., US).
• Transport encryption: TLS certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 (OV), subject Netlify, Inc, valid to 2027-03-19. It belongs to the hosting platform and says nothing about the operator.

What to Verify Next

Before any interaction, the operator should supply an independently confirmable identity and a stated purpose for the site. Any claimed financial or crypto-related offering should be checked against the relevant national financial-regulator register, using the register's own search rather than links from this site. Where this site is promoted through an advertisement, message or social profile, the referrer should be confirmed through an independent, offline route. The official channels of any brand this subdomain appears to imitate should be checked, and the domain should be compared with them. It should be re-assessed once real content is published, since the current state is not representative of what visitors may later be shown. Evidence:

• Homepage: no operator, product or contact information is published to check against.
• Domain registration: very recent creation, so no operating history exists to rely on.
• Reputation checks: the blacklist detection should be re-queried after any cleanup or content change.

Summary Verdict

The site carries an elevated risk assessment and a low trust classification. A confirmed blacklist hit, concealed form behaviour that contradicts the visible page, and an unverified, newly created identity converge on a cautionary posture. Valid encryption and reputable hosting do not offset these signals.

Infrastructure Integrity

The site sits behind AWS-based CDN and edge infrastructure, with all observed addresses belonging to shared edge servers and no origin address observable. This is a mitigating factor only, and it also prevents independent verification of where the content is actually served from. Two abuse reports were recorded against one of the shared edge addresses. They apply to the shared provider address, so they are discounted and not attributed to this site.

Closing Assessment

The site should not be used for login, credential entry, wallet connection or any financial transaction. Passive viewing is the only reasonable interaction until the operator is independently identified and the blacklist detection is cleared.

Signals weighed against the site

• AbuseIPDB: 2 reports on hosting IP 2a05:d014:58f:6200::259 (Amazon Data Services Ireland Ltd, Content Delivery Network), 0% confidence. The reports are attributed to shared infrastructure, not specifically to this website.