Is bep20-pay.netlify.app a scam? TrustSniffer's critical-risk assessment: 0/100

bep20-pay.netlify.app

Is it safe to use? An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

Download PDF Check another site How we score
Ask your AI about this report

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

Verdict

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

0 OUT OF 100
Critical Risk

bep20-pay.netlify.app shows critical-risk indicators.

Sensitive Interaction Risk Governance Risk
  • Sensitive Interaction Risk: The overall risk is high enough that entering private details here (a password, card number or wallet recovery phrase) could be unsafe.
  • Governance Risk: A registration check came back incomplete: as a site on netlify.app, this address has no registration record of its own (the platform's domain is registered, not the site). That is a gap in what could be looked up, not a sign that ownership is hidden, and it does not say who runs the site.

Evidence captured 2026-11-03, re-scored 2026-11-04 by automated analysis. Evidence confidence 75%.

How the site describes itselfA bare crypto send form for USDT with address and amount fields and a 'Next' button, branded 'Trust Wallet' but with no visible domain, operator, fee, or risk disclosure. It requests a financial transfer without verifiable context.

Evidence status and limitations

Evidence completeness: CompleteThis says whether every check on the site was recorded as finished. All of them were.

  • The evidence was captured on 2026-11-03 and re-scored on 2026-11-04. The certificate, the registration age and the page content describe the site as it was on 2026-11-03.
  • The real-world operator identity was not independently verified.

How to read these numbers

A trust score of 0 means the risk evidence outweighed every trust signal by more than the 0 to 100 scale can show. It rates the evidence found, not the probability that the site is a scam.

Evidence confidence (75%) 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.

Malware engines13 marked it maliciousVirusTotalRisk
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the CDN edge address0% confidenceAbuseIPDB, 4 reports; shared hosting inflates reports; this is the record of the CDN edge address, not of the server behind it, which was not observedNoted
First seen5 months before captureWeb archive; a site on netlify.app has no registration of its ownRisk
Web archiveArchived since 20262 snapshots; the archive has almost no record of this site, which counted against itWatch
CertificateEncrypted connectionIssued by DigiCert Global G2 TLS RSA SHA256 2020 CA1Noted

The page as captured

https://bep20-pay.netlify.app/
Screenshot of the bep20-pay.netlify.app homepage captured during the TrustSniffer assessment
What bep20-pay.netlify.app served when TrustSniffer captured it on 2026-11-03. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk, Governance Risk.
  • First seen: less than 1 year before capture (web archive; a site on netlify.app has no registration of its own).
  • Public web-archive history exists since 2026.
  • At least one reputation service TrustSniffer consulted had flagged this domain when the evidence was captured.

Full analysis

Security Alert

Fortinet, Sophos flagged this site in external intelligence checks, indicating elevated compromise/scam exposure that requires immediate caution.

Overview

This website is a single-page crypto transfer form headed "Transfer Trust Wallet". It offers a "Send USDT" function with an address-or-domain field, a "Paste" shortcut, an amount field with a "Max" button, a placeholder dollar equivalent and a "Next" button. The page carries no operator name, fee schedule, custody explanation, support channel or risk warning. Its apparent purpose is to collect a destination address and an amount from a visitor and move their funds, which is the typical mechanic of a payment-diversion or wallet-drain front.

Scam/Impersonation Risk

Contradictory signals are present and decisive. Multiple major security engines independently flag the site as malicious, and others mark it suspicious, which constitutes a confirmed blacklist condition and a hard reputational contradiction. The page presents itself under the Trust Wallet name, yet nothing on it ties it to that brand or to any identifiable operator. The wallet-style branding therefore works as unverifiable borrowed credibility attached to a fund-transfer prompt. Automated checks did not confirm brand impersonation, and no conflicting legal identities exist. The risk is nonetheless concentrated in the combination of a flagged site, a borrowed wallet name and an immediate request for a USDT transfer to a user-supplied address. A visitor who pastes an address and presses "Next" has no way to establish who controls the flow of funds, what fee applies, or whether the transfer can be reversed. The site's age and thin history do nothing to offset this. It was first observed only months ago, and its archive record is minimal. No hostile behaviour was recorded during sandbox interaction, but that cannot outweigh the external detections.

Evidence
  • Homepage: a single wallet-transfer form (address, amount, "Max", "Next") branded "Trust Wallet", with no domain, operator, fee or warning text.
  • Homepage: the page is classified as a high-stakes financial interaction with unverifiable wallet payments and unverifiable legal status.
  • Domain provenance: registration continuity of about 0.41 years (~151 days), with the first archive capture in 2026.
  • Web archive: 2 snapshots, all in 2026 (1 year tracked), which is very sparse coverage.

Regulatory Verification Notes

The site declares no licence, registration number, regulator, legal entity or jurisdiction, and it has no legal or terms pages at all. For a service that moves customer funds, this is a material disclosure gap. In this case it sits alongside confirmed adverse reputation signals, so it reinforces rather than stands apart from the cautionary conclusion. Operator identity cannot be independently connected to any real-world person or company, and ownership details are incomplete. No third-party broker or regulatory-database record corresponds to this site, so there is no external signal of authorisation. The transport certificate is valid, but it is an organisation-validated certificate issued to the hosting platform rather than to any operator of this service. It confirms encrypted transport only and says nothing about who runs the page.

Evidence
  • Homepage: no licence, regulator, company name or contact route is shown, and no terms or privacy pages exist.
  • Transport encryption: TLS certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 (OV), subject organisation Netlify, Inc, valid to 2027-03-19.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).
  • Third-party broker dataset: no matching entry.

What to Verify Next

Verification here should aim to establish whether any legitimate wallet provider is actually behind this page. Anyone who needs to use the real Trust Wallet service should reach it through the official application or the vendor's own channels, not through this page. If the link arrived by message, social post or search advertisement, the sender and the original context should be checked through an independent route. Official support channels should be confirmed offline. Any funds already sent should be treated as potentially compromised: the transaction hash should be preserved and the relevant exchange, wallet provider or authority notified promptly.

Evidence
  • Homepage: the transfer flow shows no destination domain, custody model or fee, so the receiving party cannot be identified from the page.
  • Homepage: no operator, support route or contact artifact is published to check against.
  • Homepage: the only token referenced is USDT, and the address-entry mechanic offers no confirmation of the recipient.

Summary Verdict

The overall posture is high-risk and clearly cautionary. Confirmed adverse reputation from several independent detection sources, a financial-transfer function with no verifiable operator, and the borrowed wallet branding together outweigh the few benign technical characteristics observed. The site is not treated as a legitimate wallet service, and the assessment makes no claim that its real-world operator is known.

Infrastructure Integrity

The site is hosted as a tenant on a shared platform subdomain, running on Amazon's cloud network behind CDN/WAF edge servers, and only edge addresses were observed. That is a mitigating factor only, and it cannot offset the reputation findings. Four abuse reports are recorded against one of the edge IPv6 addresses. They apply to shared provider infrastructure rather than to this site specifically and are therefore discounted, which leaves the external detections as the decisive adverse signal. Edge-only visibility also means that content on the shared platform can be swapped quickly without changing the observable infrastructure.

Closing Assessment

The site should not be used for any transfer, wallet interaction, login or entry of credentials or addresses. Passive viewing carries the least exposure, and any funds or accounts already linked to the page should be reviewed immediately.

Written analysis generated 2026-11-04 by the TrustSniffer Analysis Engine from the evidence in this report.

What the analysis found

6 findings contributed to this verdict, raised by external reputation, page content and history in the web archive.

01 External reputation

  • A confirmed external listing marks this domain as malicious: at least five security engines including a leading vendor, ten engines, or Google Safe Browsing.External reputation rule:EXT_BLACKLIST_CRITICAL

02 Page content

  • The page shows few of the signs expected from a trustworthy operator.Page content rule:PAGE_TRUST_QUALITY_LOW
  • The page content shows three or more warning signs that deceptive sites commonly use.Page content rule:PAGE_RED_FLAGS_STRONG
  • The review of the page content rated it moderate risk.Page content rule:PAGE_RISK_MED
  • The page has very little readable content.Page content rule:PAGE_CONTENT_THIN

03 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: 4 reports on hosting IP 2a05:d014:58f:6200::258 (AMAZON-02), 0% confidence. The reports are attributed to shared infrastructure, not specifically to this website.

Identity verification

StatusUNVERIFIED

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 bep20-pay.netlify.app.

  • The request stayed on bep20-pay.netlify.app. It was not redirected to another domain. Clear
  • The earliest public archive of this site is from 2026-06-04. Watch
  • It is hosted on AMAZON-02, a network registered in US. Noted

Domain intelligence

RegistrarNot available
HostingAMAZON-02 - Amazon.com, Inc.
Network registered inUS
Server IP2a05:d014:58f:6200::258 (a CDN edge address; the server behind it was not observed)
Name serversNot available
CDN / edge networkDetected (aws)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerDigiCert Global G2 TLS RSA SHA256 2020 CA1
SSL expiry2027-03-19
First seen (web archive)152 days before capture; a site on netlify.app has no registration of its own
Domain expiryNot available
Archive first seen2026-06-04 (152 days before capture)
Archive snapshots2
ReputationVirusTotal: 13 malicious | AbuseIPDB (CDN edge address, not the host): 0% confidence, 4 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about bep20-pay.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.

Already paid or signed in? Do this now

Act fast. The sooner your bank knows, the better the chance of stopping the payment.

  1. Call your bank or card company now. Use the number on the back of your card. Ask them to stop or reverse the payment.
  2. Paid with crypto? Contact the exchange or wallet app you sent it from today. Give them the address you paid.
  3. Signed in or shared a password? Change it now, on every site where you use it, and turn on two-step sign-in.
  4. Report it to the police. In the US you can also report at reportfraud.ftc.gov and ic3.gov. In other countries, use your national police or fraud reporting service.
  5. Keep the evidence. Save screenshots, receipts, emails and chat messages. Your bank and the police will ask for them.
  6. Ignore anyone who offers to get your money back for a fee. These "recovery" offers are often a second scam.

Looking for the real site? Type the company name into a search engine yourself, or use the web address printed on your card, bill or letter. Do not use links from messages or ads.

Common questions about bep20-pay.netlify.app

Is bep20-pay.netlify.app a scam?

TrustSniffer's assessment of bep20-pay.netlify.app found strong scam indicators. It scored 0 out of 100 on 2026-11-04, which is the critical-risk band. The specific signals are listed in the evidence above.

Is bep20-pay.netlify.app safe to use?

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

What is the trust score of bep20-pay.netlify.app?

bep20-pay.netlify.app scored 0 out of 100 on 2026-11-04, which places it in the critical-risk band. The score is built from the domain's age and registration history, its hosting and certificate, the content of the site itself, and third-party reputation data. There is no human rating and no user review in it.

Download this report as PDF Free, no account needed. Create one to keep a history of the sites you check.
Questions about this report? Ask your AI

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-11-04 · how we assess · report a mistake