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

# Is transbep20.vercel.app a scam? 5/100

## Verdict


**Verdict: Critical Risk, trust score 5/100.** transbep20.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-19, re-scored 2026-11-16 by automated analysis. Evidence confidence 55%.

| Field | Value |
| --- | --- |
| What the captured page showed | The page displays a 404 NOT_FOUND error stating that the page does not exist, with a DEPLOYMENT_NOT_FOUND code, a debug identifier, and links to documentation and a debug prompt copy action. It contains no service, product, login form, or commercial offer. |

## 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-19 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-19.
- 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-19; 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 transbep20.vercel.app homepage captured during the TrustSniffer assessment](https://trustsniffer.com/outputs/transbep20.vercel.app/screenshots/first.png)

_What transbep20.vercel.app served when TrustSniffer captured it on 2026-10-19. 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

This address is a subdomain on the Vercel application-hosting platform. When it was captured on 19 October 2026, it served the platform's own "404: NOT_FOUND / DEPLOYMENT_NOT_FOUND" error screen instead of any content of its own. The page showed no product, service, login form, payment flow or commercial offer, so no business model or purpose could be observed from it. The only visible items were a "Go back" link, a documentation link and a "Copy Debug Prompt" action.


### Scam/Impersonation Risk

A threat-intelligence feed listed this address as a phishing actor, with the listing last seen on 18 October 2026, the day before capture. The listing is a contradiction against the address itself, and it is what holds the assessment at critical risk. Neither the homepage nor the capture showed what the address was used for, because the page served was the hosting platform's own not-found template. That means the page gave no basis to infer credential harvesting or concealed content. The listing, not the page, carries the finding. The domain name sits under the Vercel platform's address space but is not Vercel itself, and the page offered nothing that ties it to any named organisation. No conflicting legal identities were seen, because the page names no entity. In the sandbox, one engine in the reputation scan returned a suspicious result and none returned a malicious one, so that scan is not a detection. The host-level abuse reports (82) apply to a shared Vercel address and were discounted. The sandbox runs recorded three scored behaviour findings: a strong difference in page content after interaction, and heavy external POST and XHR traffic. These belong to the platform's error template and are not evidence of the site's own conduct. All 82 requests to other hosts went to recognised services, but this is still counted as a scored finding.
_An XHR request is a request the page sends in the background while it is open, to load or send data without reloading._

Evidence:
- Threat-listing feed: the address was listed as a phishing actor, last seen 18 October 2026.
- Homepage capture: a 404 DEPLOYMENT_NOT_FOUND screen with no forms, no login field, no commercial content and no named entity.
- Reputation scan: 0 engines returned malicious and 1 returned suspicious, and Google Safe Browsing did not list the address.
- Host abuse record: 82 reports against the shared provider address 216.198.79.67, discounted as belonging to the platform's shared infrastructure.

### Regulatory Verification Notes

On the only page read, the homepage, no contact channels or terms/privacy disclosures were found. Nothing on that page identifies an operator, company, licence or jurisdiction. Because the page was a platform error template, this reflects a lack of site content more than a deliberate omission. The address is a tenant of a hosting platform and has no registration of its own, so the real-world identity behind it is unverified. No third-party broker or regulatory record was matched, and none is implied. The site's transport encryption was in place, but a standard domain-validated certificate says nothing about who runs the address.

Evidence:
- Homepage: contact channels and terms/privacy disclosures were missing on the page read, which was the only page read.
- Hosting record: the address is a vercel.app tenant, with no registration of its own.
- TLS certificate: issued by WR1 (domain-validated), and the certificate seen at capture was valid until 27 November 2026.
- Network record: served from AS16509 (AMAZON-02, Amazon.com, Inc., US).

### What to Verify Next

Anyone who received this address should first establish who sent it and why, using a channel independent of the message that carried it, such as a phone call or an in-person check. Any organisation the address claims or implies should be reached through its own official site, found independently and not through this link. If the address arrived unsolicited, it should be reported to the hosting provider's abuse channel and to the sender's organisation. A page read after 19 October 2026 may show different content from the error screen captured.

Evidence:
- Homepage: no operator or organisation is named, so there is nothing on the page to cross-check.
- Threat-listing feed: the phishing listing was last seen on 18 October 2026, so it dates from before this report.
- Hosting record: the address is a platform subdomain, so the host's abuse process is the available route.

### Summary Verdict

The address carries critical risk. A phishing-class threat listing sits against an address that presented no content of its own and no identifiable operator, and its real-world identity remains unverified. The few sound technical features observed, such as a working certificate and a resolvable network, do not offset that.


### Infrastructure Integrity

The address resolved to two IP addresses on Amazon's hosting network, with no CDN or edge vendor detected. The absence of a CDN is neutral. Network placement does not establish legitimacy, and it does not reduce the weight of the listing.


### Closing Assessment

The address should be treated as unsafe to rely on: it should not be visited from unsolicited messages or relied on as a business or service endpoint. Anything that pointed to it should be handled as a suspected phishing lure and reported.


_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.67 (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 transbep20.vercel.app.

- The request stayed on transbep20.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.67 |
| 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 transbep20.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/transbep20.vercel.app), independent automated trust & fraud analysis. Cite as https://trustsniffer.com/report/transbep20.vercel.app · assessed 2026-11-16.*
