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

Overview

This website is a subdomain on a shared static-hosting platform, with a name that suggests a cryptocurrency-related project. When visited, it shows only the hosting provider's generic "Site not found" 404 error page. There are no products, offers, contact details, legal pages or payment flows, and no visible business model. Its apparent purpose cannot be established from what it presents, and the page itself describes the address as pointing to a site that does not exist at that path.

Scam/Impersonation Risk

Contradictory signals are present. The domain is listed on an external blacklist: one reputation engine rates it malicious and a second rates it suspicious. This is the decisive negative finding and is not offset by the technical hygiene noted elsewhere. Behavioral testing adds a second concern. The page displays only a static error message, yet all three sandbox runs detected hidden forms, including password-type fields, and very large DOM changes after interaction. A genuine hosting 404 template would not be expected to behave this way, so the page may serve as a placeholder or staging layer for credential-collection content. This remains an observed anomaly, not a confirmed phishing kit. The analysis also flagged a close naming resemblance to the hosting platform's own address. That is expected for a subdomain of the platform, and no impersonation or conflicting legal identity was confirmed. Two abuse reports exist for a shared cloud edge address serving this site. They apply to infrastructure used by many tenants and are discounted, so they are not treated as evidence against this site. The domain is only weeks old and has almost no independent history, so no established track record offsets these signals. Evidence:

• Homepage: the page content is only the platform's "Site not found" notice, with no site content, forms, offers or contact channels visible to a visitor.
• Sandbox behavior: hidden forms appeared in 3 of 3 runs, 3 password-type fields were present, and up to 4,130 DOM mutations followed interaction on a page that otherwise shows only static text.
• Domain provenance: registration continuity dates to about 18 days before analysis (~0.05 years old).
• Web-archive depth: 1 snapshot, all in 2026 (1 year tracked), which is insufficient history to establish continuity.

Regulatory Verification Notes

The site discloses no operator, company name, licence, registration number, terms or privacy documentation, because the only reachable page is an error screen. Operator ownership is opaque, and nothing connects the address to a real-world business or person, so identity is unverified. Combined with the blacklist listing, this means no legitimacy can be inferred. The missing disclosures are verification gaps in their own right and are not treated as proof of fraud. No third-party broker or regulatory-database entry was matched. This absence carries no weight in either direction. Evidence:

• Homepage: no legal, about, terms or contact content is present, and no licensing claim is made.
• Hosting: the site is served from AS16509 (AMAZON-02, Amazon.com, Inc., US).
• Transport encryption: the TLS certificate is OV-validated, issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 to Netlify, Inc, and valid to 2027-03-19. This identifies the hosting platform as certificate subject, not the site's operator.
• Third-party registries: no broker or regulatory match was found for this domain.

What to Verify Next

Before any engagement, the party who directed the user to this address should be asked to supply the project's official, independently published website, and the address should be compared with it character by character. Any claimed licence, company registration or token contract should be checked directly with the relevant registry or an independent block explorer. The official support and contact channels should be confirmed through a separate, offline or previously trusted route. If the address arrived in an unsolicited message, advertisement or social-media post, it should be reported to the hosting platform's abuse desk and to the person who shared it, not explored further. Evidence:

• Homepage: no operator name, registration number or official channel is shown to check against.
• Hidden forms in the sandbox runs indicate that content other than the visible error page may be served under some conditions.
• The reputation-engine detections should be rechecked after any claimed clean-up before the address is treated as safe.

Summary Verdict

The available evidence supports a clearly cautionary, low-trust posture. A confirmed external blacklist listing, anomalous hidden-form behavior and a very recently created domain with no verifiable operator outweigh the valid encryption and mainstream hosting. The site presents no legitimate, assessable content to counterbalance these signals.

Infrastructure Integrity

The site is delivered through Amazon Web Services CDN/WAF infrastructure, and all four observed addresses are edge servers; no origin address was observable. The hosting is mainstream and the certificate is valid, which mitigates technical-compromise concerns about the delivery layer only. Edge-only visibility prevents independent verification of what sits behind the edge and can mask rapid content swaps. Protective infrastructure therefore cannot offset the reputation findings.

Closing Assessment

Interaction should be limited to passive viewing at most. Logging in, entering credentials, connecting wallets and making any payment or transfer should be avoided until the operator is independently identified and the blacklist listing 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.