---
title: "Is piyush-henna-ten.vercel.app a Scam? Trust Review, 5/100"
source: TrustSniffer
type: Website trust & fraud report
subject: "piyush-henna-ten.vercel.app"
verdict: "Critical Risk"
trust_score: 5
classification_confidence: 55
canonical_url: https://trustsniffer.com/report/piyush-henna-ten.vercel.app
assessed: 2026-11-16
evidence_captured: 2026-10-20
---

# Is piyush-henna-ten.vercel.app a scam? 5/100

## Verdict


**Verdict: Critical Risk, trust score 5/100.** piyush-henna-ten.vercel.app shows critical-risk indicators.

An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

Labels: Sensitive Interaction Risk, Governance Risk
- **Sensitive Interaction Risk:** This label is given when the overall risk is high. The captured page did not ask for a password, card number or other sensitive details; if it ever does, entering them here could be unsafe.
- **Governance Risk:** The governance checks raised a concern: the cloaking ceiling applies, but the score is below it; a threat-intelligence listing limits the score; as a site on vercel.app, this address has no registration record of its own (the platform's domain is registered, not the site). The findings below give the detail.

Evidence captured 2026-10-20, re-scored 2026-11-16 by automated analysis. Evidence confidence 55%.

| Field | Value |
| --- | --- |
| What the captured page showed | A generic 404 error page reporting that the requested page or deployment does not exist, with a 'Go back' link, a documentation link, and a debug-prompt copy button. It contains no service content, forms, or external links. |

## Evidence status and limitations


Evidence completeness: Partial

_This says whether every check on the site was recorded as finished. At least one check failed or returned no result._

- The evidence was captured on 2026-10-20 and re-scored on 2026-11-16. The certificate, the registration age and the page content describe the site as it was on 2026-10-20.
- One external source flagged this site when the evidence was captured (a threat-intelligence listing from a feed TrustSniffer monitors (phishing, the site itself as the source, last seen 2026-10-18)). No second source confirms it. The alert is from the evidence captured on 2026-10-20; it was not re-queried for this version and is treated as unconfirmed. On its own the alert would limit the score to at most 49; the threat-listing ceiling holds it at 5, because the listing names the site itself as the source.
- When captured, this address served the hosting platform's own 'site not found' page; the page and sandbox findings below were measured on that page.
- The real-world operator identity was not independently verified.
- These checks returned no result: web archive lookup.

### How to read these numbers

The trust score runs from 0 to 100, higher is safer. 5/100 rates the evidence found, not the probability that the site is a scam.

Evidence confidence (55%) measures how much of TrustSniffer's evidence set this site produced: the page reading, the browser sandbox, the web archive, the registration record and the reputation services. It falls when a check returns nothing, as listed above, and it does not change the score.


## At a glance

The checks that decide most of this verdict.

| Check | Result | Status |
| --- | --- | --- |
| What limits the score | Threat-listing ceiling (A threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-18), and that listing caps the score. The cloaking ceiling and the unconfirmed alert ceiling (at most 49) also apply, but the score is below them.) | Risk |
| Malware engines | None malicious; 1 marked it suspicious (VirusTotal) | Watch |
| Google Safe Browsing | Not listed (Google) | Clear |
| Abuse reports on the host | 0% confidence (AbuseIPDB, 82 reports; shared hosting inflates reports) | Clear |
| Domain age | Not available (No registration record was returned) | Noted |
| Certificate | Encrypted connection (Issued by WR1) | Noted |
| Hosted by | AMAZON-02 (Network registered in US) | Noted |

## The page as captured


![Screenshot of the piyush-henna-ten.vercel.app homepage captured during the TrustSniffer assessment](https://trustsniffer.com/outputs/piyush-henna-ten.vercel.app/screenshots/first.png)

_What piyush-henna-ten.vercel.app served when TrustSniffer captured it on 2026-10-20. The page may look different now._

## Key findings


- Automated classification: Sensitive Interaction Risk, Governance Risk.
- No security engine marked this domain as malicious and Google Safe Browsing does not list it; some engines marked it suspicious, which TrustSniffer does not count as a listing. Its hosting IP carries AbuseIPDB reports below the confidence level TrustSniffer treats as a flag.
- The operator behind the site could not be independently connected to a real-world brand or person.

## Full analysis


### Overview

The address is a tenant subdomain on the Vercel hosting platform. It is not Vercel itself, even though the name carries that brand. When captured on 20 October 2026, the homepage returned only the platform's own "deployment not found" error page. The page had a short notice that the content does not exist, a "Go back" link, a documentation link and a debug-prompt copy button. It showed no products, prices, forms, contact details or business description, so no business model can be inferred.


### Scam/Impersonation Risk

A threat-intelligence feed listed this address as a **phishing** source, with the site itself in the acting role, and last saw it on 18 October 2026. This is a single-source listing. Safe Browsing did not list the address, and no engine rated it malicious. One VirusTotal engine rated it suspicious, and that is not a detection. The assessment is **critical risk**, and the score is held down by the threat-listing ceiling. Phishing is the listed class, but the page captured on 20 October 2026 showed no login or password form and no data-collection form. The address served only the platform's not-found template. The network measurements recorded during the capture (heavy third-party requests and a strong content-change reading after interaction) belong to that template. They are not evidence of what the operator's own pages do. No brand impersonation, conflicting legal identities or compromised-site indicators were confirmed. The listing is a single, unconfirmed alert dated 18 October 2026, two days before the capture, and the address served no content of its own when captured.

Evidence:
- Threat-intelligence listing: phishing class, site in the acting role, last seen 2026-10-18; this is the only source for the listing.
- VirusTotal: 0 engines malicious and 1 suspicious; Google Safe Browsing did not list the address.
- Homepage capture: platform "404 DEPLOYMENT_NOT_FOUND" page, 198 characters of text, 0 forms and 0 outbound links.
- The registration record shows a platform-hosted subdomain with no registration of its own.

### Regulatory Verification Notes

On the single page read (the homepage), the site made no licence or registration claims. It also published no contact channels, terms or privacy policy on the pages read. The address returned only a platform error page, so no legal-identity pages could be assessed. No third-party broker or regulatory source matched this address, and identity has not been independently verified. Nothing links the address to a named business or person. Transport security is present but does not establish who operates the address.

Evidence:
- Homepage: contact channels and terms or privacy pages were not present on the pages read.
- Homepage: no licence, registration number or company name was displayed.
- TLS certificate: domain-validated (DV), issued by WR1, seen at capture as valid to 2026-11-27. DV validation confirms control of the domain, not the operator's identity.
- Hosting: served from AS16509 (Amazon).

### What to Verify Next

Whoever owns the content should first confirm whether the deployment was removed deliberately or abandoned. Any party considering engagement should obtain the operator's identity and official channels from a source independent of this address. Examples are a direct approach to the organisation the link claims to represent, or its officially published website reached by typing the address manually. Any message, advertisement or link that directed a person to this address should be checked against that independent channel before any action is taken.

Evidence:
- Homepage: the address served no content when captured, so no operator claims were available to test.
- Threat listing: the phishing listing was last seen 2026-10-18, so any link that led here deserves scrutiny of how it was delivered.
- Hosting record: the address is a subdomain of a shared platform, so the platform's own domain gives no information about this tenant.

### Summary Verdict

The address sits at a critical risk posture. A phishing listing and an unverified identity are not offset by the lack of content or by technical hygiene. The score is held down by the threat-listing ceiling, and the address served no content of its own when captured.


### Infrastructure Integrity

The address resolved to two origin-type IP addresses on Amazon's hosting network, delivered through the Vercel platform. No CDN or edge vendor was detected. The host address's abuse record was checked. It carried 82 reports, but they belong to the provider's shared address and were discounted. They are not attributed to this site. The infrastructure is neutral and does not offset the threat listing.


### Closing Assessment

The address should be treated as unsuitable for any interaction. Any link that points to it should not be followed, and no information should be submitted to anything it later serves. If an organisation is believed to be behind it, contact should go through that organisation's independently confirmed channels.


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

## What the analysis found

7 findings contributed to this verdict, raised by governance, behaviour in a sandbox, page content, and registration and ownership.

_When captured, this address served the hosting platform's own 'site not found' page; the page and sandbox findings below were measured on that page._

### 01 Governance
- The page showed different content to different visitor profiles during the sandbox session, and a separate warning sign backs that up, so the score is capped. This ceiling applies, but the score is below it, so it does not set the score. (Governance `rule:GOV_CLOAKING`)
- A threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-18), and that listing caps the score. (Governance `rule:gov_active_threat_listing`)

### 02 Behaviour in a sandbox
- During the sandbox session the page showed markedly different content to different visitor profiles. This can have ordinary causes such as bot defence, and it can also hide content from checks. (Behaviour in a sandbox `rule:BEHAV_CLOAKING_STRONG`)
- The page made many background requests to other domains while it was open. (Behaviour in a sandbox `rule:BEHAV_EXTERNAL_XHR_HEAVY`)
- The page sent data to other domains many times while it was open. (Behaviour in a sandbox `rule:BEHAV_EXTERNAL_POSTS_HEAVY`)

### 03 Page content
- The page has very little readable content. (Page content `rule:PAGE_CONTENT_THIN`)
- The page runs on a free hosting-platform address instead of a domain of its own, a setup common to short-lived phishing and claim pages. (Page content `rule:PAGE_FREE_PLATFORM_ADDRESS`)

### 04 Registration and ownership
- As a site on vercel.app, this address has no registration record of its own (the platform's domain is registered, not the site). (Registration and ownership `rule:KF_WHOIS_INCOMPLETE`)

### How related findings were counted

Some findings above describe the same underlying fact, and some are weak on their own. TrustSniffer counts each such group under one shared limit, so one fact is not counted several times and weak signals stay bounded.

- Third-party connections: 2 findings share one limit, because they all measure one fact: the page loads files from other hosts. Together they stayed under the limit.

### Noted, not counted

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

- AbuseIPDB: 82 reports on hosting IP 216.198.79.3 (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.

## What TrustSniffer observed

First-party facts recorded during the assessment of piyush-henna-ten.vercel.app.

- The request stayed on piyush-henna-ten.vercel.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 | 216.198.79.3 |
| Name servers | Not available |
| CDN / edge network | Not detected |
| Resolved IP addresses | 2 |
| Edge IP addresses | 0 |
| Likely origin IP addresses | 2 |
| SSL issuer | WR1 |
| SSL expiry | 2026-11-27 |
| First seen (web archive) | Not available (the web archive has no record of this address; a site on vercel.app has no registration of its own) |
| Domain expiry | Not available |
| Archive first seen | Not available |
| Archive snapshots | Not counted (archive lookup incomplete) |
| Reputation | VirusTotal: 0 malicious, 1 suspicious \| AbuseIPDB: 0% confidence, 82 reports \| Google Safe Browsing: 0 matches |

## About this assessment


**Was this report useful?** Tell other people what you think of TrustSniffer, good or bad. An honest review helps others decide whether to rely on these checks. [Review TrustSniffer on Trustpilot](https://www.trustpilot.com/review/trustsniffer.com)

A trust score summarises the evidence TrustSniffer could collect about piyush-henna-ten.vercel.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
- [Other websites assessed as low trust or critical risk](https://trustsniffer.com/directory/phishing-domains), phishing is among the evidence in this report
- [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
- [How to Report a Scam Website: Who to Tell and Why](https://trustsniffer.com/blog/how-to-report-a-scam-website)
- [Scam Website Statistics: Inside Our Data](https://trustsniffer.com/blog/scam-website-statistics-trustsniffer-data)
- [What Are Website Trust Signals?](https://trustsniffer.com/blog/website-trust-signals-explained)

---
*Source: [TrustSniffer](https://trustsniffer.com/report/piyush-henna-ten.vercel.app), independent automated trust & fraud analysis. Cite as https://trustsniffer.com/report/piyush-henna-ten.vercel.app · assessed 2026-11-16.*
