---
title: "crypto-zx1.netlify.app: Analysis Blocked, No Trust Score"
source: TrustSniffer
type: Website trust & fraud report
subject: "crypto-zx1.netlify.app"
verdict: "Needs Review"
classification_confidence: 75
canonical_url: https://trustsniffer.com/report/crypto-zx1.netlify.app
assessed: 2026-10-21
---

# crypto-zx1.netlify.app: analysis blocked, no trust verdict

## Verdict


**Verdict: Needs Review.** crypto-zx1.netlify.app blocked our automated scan and could not be verified.

The site blocked our scan, so nothing was confirmed either way. Treat it as unknown and verify who runs it another way.

Labels: Needs Review
- **Needs Review:** The site blocked or cut short the capture, so no verdict was reached.

Assessed 2026-10-21 by automated analysis.

**This site blocked our automated check. You can finish it.** Sites behind Cloudflare and similar walls often block automated checks. Install the free TrustSniffer extension for Chrome, open crypto-zx1.netlify.app, open the extension and choose "Analyze this page". It reads the page in your own browser, removes private details before anything is sent, and completes this report. [Get the Chrome extension](https://chromewebstore.google.com/detail/trustsniffer-website-wall/fmfhhkejepikfjnijabckbloialimdmi)

| Field | Value |
| --- | --- |
| How the site describes itself | The page is a Netlify 'Site not found' 404 placeholder indicating that the requested site or path does not exist. It contains no login form, product, pricing, or commercial content. |

## Evidence status and limitations


Evidence completeness: Incomplete

_This says whether every check on the site was recorded as finished. The site blocked or cut short our capture, so the result needs review._

- Capture was incomplete or blocked; this result requires review.
- The real-world operator identity was not independently verified.

## At a glance

The checks that decide most of this verdict.

| Check | Result | Status |
| --- | --- | --- |
| Malware engines | None flagged it (VirusTotal) | Clear |
| Google Safe Browsing | Not listed (Google) | Clear |
| Abuse reports on the CDN edge address | 0% confidence (AbuseIPDB, 2 reports; shared hosting inflates reports; this is the record of the CDN edge address, not of the server behind it, which was not observed) | Noted |
| First seen | 18 days before capture (Web archive; a site on netlify.app has no registration of its own) | Risk |
| Web archive | 4 snapshots (4 snapshots; the archive has almost no record of this site, which counted against it) | Watch |
| Certificate | Encrypted connection (Issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1) | Noted |

## The page as captured


![Screenshot of the crypto-zx1.netlify.app homepage captured during the TrustSniffer assessment](https://trustsniffer.com/outputs/crypto-zx1.netlify.app/screenshots/first.png)

_What crypto-zx1.netlify.app served when TrustSniffer captured it on 2026-10-21. The page may look different now._

## Key findings


- The site blocked automated access, so TrustSniffer could not collect enough evidence to assign a score.

## Full analysis


### Overview

This website is a subdomain on the Netlify hosting platform. When visited, it shows only the platform's standard "Site not found" 404 placeholder, which says the requested address does not exist and invites visitors to start building their own site. It presents no products, pricing, branding, login, contact details or calls to action, and it shows no monetization model. Its apparent purpose cannot be determined from what it publishes, even though the subdomain name suggests a crypto-related project.


### Scam/Impersonation Risk

No contradictions were observed. There is no confirmed phishing, no conflicting legal identities, no brand impersonation and no confirmed threat listing. The platform-owned name of the placeholder page accounts for the lookalike similarity to the hosting brand. One security engine returned a single, unconfirmed "suspicious" rating. Two abuse reports exist, but they attach to a shared cloud-network address used by many tenants, not to this site specifically, so they carry little weight. The more meaningful concern is behavioral. The visible page contains no form, yet automated sessions detected concealed form elements, including password-type fields, in every run. The same sessions recorded very heavy page restructuring after interaction, several console errors, and extensive external network activity. This may be scaffolding from the hosting platform's error template, but the sandbox could not attribute it. A page that visibly offers nothing while carrying credential-capable elements is an unexplained discrepancy. A crypto-themed subdomain on a free hosting tier that is very new also gives little basis for assuming good faith. Together these keep the assessment at "needs review", and they do not amount to a finding of fraud.
_A console error is a technical error message that the page's own code reported inside the browser while it ran. It describes how the page is built, and on its own it is not proof that the site is harmful._

Evidence:
- Homepage: Netlify "Site not found" 404 placeholder with no forms, products, contact details or commercial content visible.
- Behavioral sessions (3 of 3 runs): hidden forms detected each time, with 3 password-type fields recorded and about 4,130 DOM mutations after interaction.
- Domain provenance: first observed about 19 days before analysis (~0.05 years); 4 archive snapshots, all in 2026 (1 year tracked).
- Reputation checks: no confirmed vendor detections, one unconfirmed "suspicious" rating, and 2 abuse reports on a shared CDN address, which were discounted.

### Regulatory Verification Notes

The page carries no legal or identity content, so no operator, company name, terms, privacy policy or licensing claim exists to assess. The site claims no regulated status, and no third-party broker record matches it. The operator identity therefore stays independently unconnected to any real-world person or business, and legitimacy can only be described as unestablished. This is a verification gap. It is not evidence of wrongdoing on its own. The TLS certificate is valid and of organization-validated grade. It is issued to the hosting platform, not to the site's operator, so it confirms the encryption and the platform but says nothing about who runs this subdomain.

Evidence:
- Homepage: no company name, registration number, licence reference, terms page or privacy page is presented.
- Transport encryption: TLS certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 (OV), subject organization Netlify, Inc, valid to 2027-03-19 (149 days remaining at analysis).
  _A TLS certificate is what puts the padlock and https:// in your browser and encrypts the connection. "DigiCert Global G2 TLS RSA SHA256 2020 CA1" is the name of the authority that issued it. OV (organization validated) means the issuer also checked the organization that runs the site. "Valid to" is the date it expires._
- Hosting: served from AS16509 (AMAZON-02 – Amazon.com, Inc., US), a US-registered (ARIN) network.
- Third-party broker dataset: no matching record.

### What to Verify Next

Anyone who received this address should first ask the sender which site was intended and confirm the correct address through a separate, independent channel. A 404 usually means a mistyped link, a removed deployment or a project not yet published. The next step is to re-check the address after the sender confirms it. If it begins serving a financial or crypto offering, the operator's legal identity and any claimed licence should be confirmed with the relevant regulator's public register before engaging. Any later official contact channels should be confirmed through an independent route.

Evidence:
- Homepage: the platform's own text states the requested path does not exist, and it offers no operator contact.
- Archive record: only 4 snapshots, all in 2026, so there is no earlier content to compare against.
- Behavioral sessions: concealed form elements may appear differently once a real site is deployed, so the address should be re-assessed then.

### Summary Verdict

The available evidence supports a posture of unknown entity, pending review: nothing contradicts the site, but nothing affirmatively establishes it either. The page offers no substance on which trust could be built, and the unexplained concealed form elements and the very recent first observation keep it from rising above that posture. The assessment is likely to change once a real site is deployed and its operator becomes identifiable.


### Infrastructure Integrity

The site sits behind AWS-based content-delivery infrastructure, and every observed address is an edge node. It runs on a reputable, mainstream cloud platform with a valid certificate from a well-known issuer, which is a mitigating factor. This protection is not evidence of legitimacy. Because only edge nodes are visible, the underlying hosting cannot be independently verified, and the content behind the address could be swapped quickly without any visible infrastructure change.


### Closing Assessment

Ordinary caution is proportionate: the address should be treated as unconfirmed until the intended destination and its operator are established independently. No credentials, payment details or wallet connections should be supplied to it before that confirmation, and the site should be re-assessed once it serves real content.


_Written analysis generated 2026-10-21 by the TrustSniffer Analysis Engine from the evidence in this report._

## What the analysis found

6 findings contributed to this verdict, raised by behaviour in a sandbox, hosting and network, page content and history in the web archive.

### 01 Behaviour in a sandbox
- The page contained a form a visitor cannot see. (Behaviour in a sandbox `rule:BEHAV_HIDDEN_FORMS`)
- The page contained a form a visitor cannot see in more than one sandbox session. (Behaviour in a sandbox `rule:BEHAV_HIDDEN_FORMS_REPEAT`)

### 02 Hosting and network
- The domain was registered, or a site on a hosting platform was first seen, less than three months before capture. (Hosting and network `rule:DNS_NEW_DOMAIN_90D`)

### 03 Page content
- The page shows few of the signs expected from a trustworthy operator. (Page content `rule:PAGE_TRUST_QUALITY_LOW`)
- The page runs on a free netlify.app address instead of a domain of its own, a setup common to short-lived phishing and claim pages. (Page content `rule:PAGE_BRAND_SUSPECTED`)

### 04 History in the web archive
- The web archive has almost no record of this domain, which fits a site that is new. (History in the web archive `rule:ARCH_PEN_YOUNG_AND_SPARSE`)

### Noted, not counted

Recorded during the assessment, but not counted against the site.

- AbuseIPDB: 2 reports on hosting IP 2a05:d014:58f:6200::259 (AMAZON-02), 0% confidence. The reports are attributed to shared infrastructure, not specifically to this website.

## Identity verification


| Field | Value |
| --- | --- |
| Status | UNVERIFIED |

The operator behind the site could not be connected to a real-world brand or person. What the page shows, if anything, is listed below; none of it was independently checked.

- No contact detail, company registration number or linked social profile was extracted from the page for checking. Any operator the page names in its own words (see how the site describes itself, above) is not verified here.

## What TrustSniffer observed

First-party facts recorded during the assessment of crypto-zx1.netlify.app.

- The request stayed on crypto-zx1.netlify.app. It was not redirected to another domain. (Clear)
- It is hosted on AMAZON-02, a network registered in US. (Noted)

## Domain intelligence


| Field | Value |
| --- | --- |
| Registrar | Not available |
| Hosting | AMAZON-02 - Amazon.com, Inc. |
| Network registered in | US |
| Server IP | 2a05:d014:58f:6200::259 (a CDN edge address; the server behind it was not observed) |
| Name servers | Not available |
| CDN / edge network | Detected (aws) |
| Resolved IP addresses | 4 |
| Edge IP addresses | 4 |
| Likely origin IP addresses | 0 |
| SSL issuer | DigiCert Global G2 TLS RSA SHA256 2020 CA1 |
| SSL expiry | 2027-03-19 |
| First seen (web archive) | 18 days before capture; a site on netlify.app has no registration of its own |
| Domain expiry | Not available |
| Archive first seen | Not available |
| Archive snapshots | 4 |
| Reputation | VirusTotal: 0 malicious \| AbuseIPDB (CDN edge address, not the host): 0% confidence, 2 reports \| Google Safe Browsing: 0 matches |

## About this assessment


A trust score summarises the evidence TrustSniffer could collect about crypto-zx1.netlify.app at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A high score means the signals were consistent with a legitimately operated site; a low or critical score means several risk patterns were present. It is a starting point for your own judgement, not a guarantee and not a legal finding. There is no human rating and no user review in it. A site can change after it is assessed.

## Related on TrustSniffer
- [Every website and wallet TrustSniffer has assessed](https://trustsniffer.com/directory), the full risk directory
- [Check another website](https://trustsniffer.com/web-intelligence), run a new assessment
- [Check a crypto wallet address](https://trustsniffer.com/on-chain-risk), on-chain screening
- [The TrustSniffer Risk Index](https://trustsniffer.com/stats), how this verdict compares

## Guides
- [What Are Website Trust Signals?](https://trustsniffer.com/blog/website-trust-signals-explained)
- [How to Check if a Website Is Legit](https://trustsniffer.com/blog/how-to-check-if-a-website-is-legit)
- [How the TrustSniffer Trust Score Works](https://trustsniffer.com/blog/how-trustsniffer-trust-score-works)

---
*Source: [TrustSniffer](https://trustsniffer.com/report/crypto-zx1.netlify.app), independent automated trust & fraud analysis. Cite as https://trustsniffer.com/report/crypto-zx1.netlify.app · assessed 2026-10-21.*
