Is send-bep-usdt-bsc.vercel.app a scam? TrustSniffer's high-risk assessment: 1/100

send-bep-usdt-bsc.vercel.app
Download PDF Check another site How we score

Verdict

This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.

1 OUT OF 100
Critical Risk

send-bep-usdt-bsc.vercel.app shows high-risk / scam indicators.

Sensitive Interaction Risk Governance Risk

Assessed 2026-10-22 by automated analysis. Classification confidence 75%.

Evidence status and limitations

Evidence completeness: Not recorded

  • The real-world operator identity was not independently verified.
  • Module-level completeness metadata is unavailable for this legacy report.

At a glance

The checks that decide most of this verdict.

Malware engines17 flagged itVirusTotalRisk
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the host0% confidenceAbuseIPDB, 81 reports; shared hosting inflates reportsClear
Domain age29 days oldMost scam domains are under a year oldRisk
Web archiveArchived since 20261 snapshotClear
CertificateEncrypted connectionIssued by WR1Noted

The page as captured

https://send-bep-usdt-bsc.vercel.app/
Screenshot of the send-bep-usdt-bsc.vercel.app homepage captured during the TrustSniffer assessment
What send-bep-usdt-bsc.vercel.app served when TrustSniffer captured it on 2026-10-22. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk.
  • Domain age: less than 1 year (registration continuity).
  • Public web-archive history exists since 2026.
  • At least one reputation service TrustSniffer consulted had flagged this domain at assessment time.

Full analysis

Security Alert

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

This website is an auto-generated subdomain on a public application-hosting platform. Its hostname describes sending USDT over the BEP-20 standard on the BNB Smart Chain. When reviewed, the homepage showed only a "Deployment Unavailable" placeholder with a few lines of text, and the host returned a restricted-access response. No product, brand, company or service is described, so the apparent purpose can only be inferred from the hostname, which reads like a stablecoin transfer or payment-collection page.

Scam/Impersonation Risk

The assessment rests on external threat intelligence, because the page itself exposed almost nothing to analyse. A substantial number of security engines currently flag the site as malicious, including several tier-one vendors, and it is confirmed on blacklists. This is a hard contradiction and the decisive factor in the assessment. The hostname combines an action phrase ("send"), a token standard and a named blockchain on a free, disposable subdomain. That is a common construction for crypto-transfer lures, and it also resembles the hosting platform's own domain, which adds a lookalike element. The reputation evidence does not show which scheme is involved, and sandbox testing recorded no wallet-connection, clipboard-manipulation or external form-posting behaviour. That test ran against a placeholder page, so it is weak assurance. The detections remain the controlling signal. No conflicting legal identities were observed, because the page presents no identity at all. Evidence:

  • Homepage: the page title is "Deployment Unavailable" and the only content is a short placeholder message, so the page offers no verifiable business function.
  • Reputation checks: multiple independent security engines classify the host as malicious, and it appears on external blacklists. A kill-switch condition was triggered by the volume of detections.
  • Web archive: a single snapshot, first and last seen on 2026-09-22 (about 29 days tracked), and no earlier history for the host.
  • Sandbox: three clean runs showed zero external requests and no wallet-provider activity, with three console errors, consistent with a stub page.

Regulatory Verification Notes

The only page available carries no legal entity name, licensing statement, registration number, terms or privacy policy. Operator identity could not be tied to any real-world brand or person, and ownership is opaque. For a site whose hostname implies handling digital-asset transfers, that is a significant content gap, and it compounds the reputational findings above. No third-party broker or regulatory listing matched this host, so no external reputational context exists on this point. Evidence:

  • Homepage: no company name, jurisdiction, licence or contact disclosure appears.
  • Transport security: the TLS certificate is issued by WR1 at domain-validation level only, valid to 2026-11-27 (36 days remaining). This confirms encryption but says nothing about the operator.
  • Network origin: served from AS16509 (AMAZON-02, Amazon.com, Inc., US), registry ARIN.

What to Verify Next

No engagement should proceed on the strength of this host. Anyone who received a link to it should establish its source through an independent, offline route. They should confirm with the supposed counterparty, using previously known contact details, that the payment instructions are genuine. Any wallet address or transfer request associated with the link should be treated as unauthorised until confirmed. Organisations should re-check the reputation status after the placeholder is replaced or removed, since the content could change. Evidence:

  • Homepage: no named counterparty or official channel is presented that could be used for confirmation.
  • Hostname: the transfer-related wording suggests the link was likely distributed to a specific recipient, so its origin is the key fact to establish.
  • Threat intelligence: detections are current as of this assessment and may change if the deployment changes.

Summary Verdict

The site carries a critical, high-risk trust posture. Strong external threat detections and confirmed blacklisting outweigh every neutral or mitigating technical signal, and no content exists that could establish legitimacy or operator identity. The site is treated as hostile, and interaction beyond passive observation is outside the safe range.

Infrastructure Integrity

The site is delivered through the hosting platform's edge network on Amazon-operated address space. It uses a valid but basic certificate, and the true origin server is not observable. This is a mitigating factor only and does not offset the reputation findings. A large number of abuse reports apply to the shared edge address. They are attributed to the platform's shared infrastructure rather than this site and were discounted, so they do not add to the risk assessment. However, the shared, disposable nature of the platform allows content to be swapped quickly, which limits independent verification.

Closing Assessment

Passive viewing is the only acceptable interaction. Logging in, entering credentials, connecting a wallet, and sending funds or tokens should all be avoided. Any link to this host should be reported to the platform's abuse team and to internal security.

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

What the analysis found

4 findings contributed to this verdict, raised by external reputation, hosting and network, history in the web archive, registration and ownership.

01 External reputation

  • An external threat feed lists this domain: either Google Safe Browsing marked it malicious, or a significant number of malware engines flagged it.External reputation rule:EXT_BLACKLIST_CRITICAL

02 Hosting and network

  • The domain was registered less than three months ago.Hosting and network rule:DNS_NEW_DOMAIN_90D

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

04 Registration and ownership

  • The public registration record for this domain is incomplete.Registration and ownership rule:KF_WHOIS_INCOMPLETE

Signals weighed against the site

  • AbuseIPDB: 81 reports on hosting IP 64.29.17.131 (Vercel, Inc, Content Delivery Network), 0% confidence. The reports are attributed to shared infrastructure, not specifically to this website.

Identity verification

StatusUNKNOWN
Identity score50/100
Identity verification confidence30%
  • AI page analysis unavailable (page captured; identity not AI-verified)

Identity verification measures whether the site can be independently connected to a real-world brand or person. It is separate from the classification confidence.

What TrustSniffer observed

First-party facts recorded during the assessment of send-bep-usdt-bsc.vercel.app.

  • The request stayed on send-bep-usdt-bsc.vercel.app. It was not redirected to another domain. Clear
  • The earliest public archive of this site is from 2026-09-22. Clear
  • It is hosted on AMAZON-02, from a server in US. Noted

Domain intelligence

RegistrarNot available
HostingAMAZON-02 - Amazon.com, Inc., US
CountryUS
Server IP64.29.17.131
Name serversNot available
CDN / edge networkDetected
Resolved IP addresses6
Edge IP addresses6
Likely origin IP addresses0
SSL issuerWR1
SSL expiry2026-11-27
Domain age0.08 years (continuous registration)
Domain expiryNot available
Archive first seen2026-09-22
Archive snapshots1
ReputationVirusTotal: 17 flagged | AbuseIPDB: 0% confidence, 81 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about send-bep-usdt-bsc.vercel.app at assessment time. It is a starting point for your own judgement, not a guarantee: a high score means the signals were consistent with a legitimately operated site, a low or critical score means several risk patterns were present.

TrustSniffer assesses a website from the evidence it can collect at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A score is a summary of that evidence, 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 send-bep-usdt-bsc.vercel.app

Is send-bep-usdt-bsc.vercel.app a scam?

TrustSniffer's assessment of send-bep-usdt-bsc.vercel.app found strong scam indicators. It scored 1 out of 100 on 2026-10-22, which is the critical-risk band. The specific signals are listed in the evidence above.

Is send-bep-usdt-bsc.vercel.app safe to use?

This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.

What is the trust score of send-bep-usdt-bsc.vercel.app?

send-bep-usdt-bsc.vercel.app scored 1 out of 100 on 2026-10-22, 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.
By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-10-22 · how we assess · report a mistake