Is betpotwins.web.app a scam? 5/100

betpotwins.web.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.

5 OUT OF 100
Critical Risk

betpotwins.web.app shows critical-risk indicators.

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: a threat-intelligence listing limits the score; as a site on web.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.

Assessed 2026-11-13 by automated analysis. Evidence confidence 55%.

How the site describes itselfBETPOT presents itself as a prediction protocol with a jackpot and $SOL rewards. It asks visitors to connect a wallet to claim rewards, is labelled DEVNET, and offers only a testnet guide. It shows no legal entity, contact, terms, or risk warning.

Evidence status and limitations

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

  • 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-26)). No second source confirms it. The alert is from the evidence captured on 2026-11-13 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.
  • The real-world operator identity was not independently verified.

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.

What limits the scoreThreat-listing ceilingA threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-26), and that listing caps the score. The unconfirmed alert ceiling (at most 49) also applies, but the score is below it.Risk
Malware enginesNone malicious; 1 marked it suspiciousVirusTotalWatch
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the CDN edge address1% confidenceAbuseIPDB, 3 reports; shared hosting inflates reports; this is the record of the CDN edge address, not of the server behind it, which was not observedNoted
Domain ageNot availableNo registration record was returnedNoted
Web archiveNever archivedNo public history of this siteWatch
CertificateEncrypted connectionIssued by WR3Noted

The page as captured

https://betpotwins.web.app/
Screenshot of the betpotwins.web.app homepage captured during the TrustSniffer assessment
What betpotwins.web.app served when TrustSniffer captured it on 2026-11-13. 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

BETPOT is a single-page crypto prediction and jackpot betting landing site that calls itself a "Prediction Protocol" and is built around the Solana ecosystem. The page shows navigation for a jackpot, markets, a how-it-works section and a testnet guide. Its one call to action asks the visitor to connect a wallet to claim a "$SOL reward". The apparent model is wagering on predictions and a jackpot paid in $SOL, but the page does not say how it earns revenue, how stakes work or who runs it.

Scam/Impersonation Risk

This is a critical risk. A threat-intelligence entry classes the site as an active phishing actor, last seen on 26 October 2026. The entry is a single alert, so it is not independently corroborated. It is the contradictory signal that matters here, and the overall score is held down by the threat-listing ceiling. One security engine also returned a suspicious verdict, and none returned a malicious one. The homepage supports the concern. It tells the visitor to "connect your wallet to claim $SOL reward" while the same page carries a "DEVNET" label and a "Testnet Guide". The site's own page therefore offers a reward claim on what it labels a test network. It also shows a jackpot and a reward claim with no stated rules, operator or risk disclosure. Reward claims that depend on a wallet connection are the typical entry point for phishing and wallet-draining schemes. No sandbox run observed wallet-drainer activity, clipboard tampering or hidden forms. That does not offset the listing, because the page is too thin to show what a connection would trigger. No brand impersonation and no conflicting legal identities were observed. The concern rests on the phishing classification and on the page's lack of substance.

Evidence
  • Threat-intelligence entry: phishing class, role as actor, last seen 26 October 2026, single source.
  • VirusTotal: 0 malicious and 1 suspicious engine result.
  • Homepage: the quoted "Please connect your wallet to claim $SOL reward" appears beside the DEVNET label, with no rules for the "BetJackpot" feature.
  • Behavioural sandbox: 3 successful runs recorded 9 console errors, which is a scored finding. The page has no forms and no login fields.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.

Regulatory Verification Notes

A prediction or betting service is expected to disclose a legal entity, a registration or licence, a regulator, terms or a privacy policy, and a risk warning. On the one page read, the homepage, none of these five disclosures was present. The only identity the page offers is the name BETPOT, in the page title and in the "© 2026 BETPOT" footer. That is a self-description and does not connect the site to any real-world operator, so the operator's identity remains unverified. The page also states no contact route. No licence is claimed, so no licence could be checked. The site is a tenant on a hosting platform's shared domain and has no registration of its own. Registration privacy and the missing page meta description are both scored findings. No third-party broker or regulatory source matched the name.

Evidence
  • Homepage: about 217 characters of visible text, with no legal entity, licence, regulator, terms, privacy policy or risk warning.
  • Homepage: no contact method, no address and no meta description.
  • Hosting record: served from AS54113 (Fastly, US), on a hosting platform's shared domain.
  • Transport encryption: the TLS certificate was issued by WR3 at domain-validation level, valid to 2027-01-25. This confirms an encrypted connection only, not who operates the site.

What to Verify Next

Before any interaction, confirm independently whether a real operator exists. That means checking the gambling or prediction-market registers of the regulators in the visitor's own jurisdiction for BETPOT, since the page names no regulator. Any operator name, licence or support channel should be obtained from a source outside the site and then confirmed offline. Claims of $SOL rewards should be treated as unsubstantiated until an operator publishes rules, stake mechanics and a risk warning. The DEVNET label means that anything shown on this page should not be assumed to carry real value or to be redeemable.

Evidence
  • Homepage: the "Testnet Guide" and DEVNET label are the only mechanics information offered.
  • Homepage: no operator, rules, terms or risk warning appear on the page read.

Summary Verdict

The site is a critical risk. The phishing-class threat entry and the near-empty, unverifiable page reinforce each other, and no positive evidence of legitimacy outweighs them. Its technical basics are routine and do not speak to who runs it or what it does with a visitor's wallet.

Infrastructure Integrity

The site is delivered through Fastly, and all observed addresses, one IPv4 and one IPv6, are CDN edge addresses, so the origin host was not observable. The CDN is a neutral factor here. Three abuse reports on the shared provider's IPv6 address relate to that shared address and do not point to this site specifically. A valid certificate from a known issuer and a recognised network identify standard delivery plumbing, not trustworthy operation, and neither offsets the other findings.

Closing Assessment

Do not connect a wallet, sign any transaction or send funds through this site. Visitors who need to look at the page should do so read-only and without interacting with the "Connect Wallet" prompts.

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

What the analysis found

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

01 Governance

  • 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-26), and that listing caps the score.Governance rule:gov_active_threat_listing

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 page has very little readable content.Page content rule:PAGE_CONTENT_THIN
  • The page has no description for search engines, which established sites usually provide.Page content rule:PAGE_SEO_MISSING_META

03 Behaviour in a sandbox

  • The page produced an unusually high number of errors while it ran.Behaviour in a sandbox rule:BEHAV_CONSOLE_ERRORS_HIGH

04 Registration and ownership

  • As a site on web.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.

  • Page quality: 2 findings share one limit, because each is weak evidence on its own. Together they stayed under the limit.

Noted, not counted

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

  • AbuseIPDB: 3 reports on hosting IP 2620:0:890::100 (FASTLY), 1% 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.

  • org:BETPOT
  • on_site_identity

What TrustSniffer observed

First-party facts recorded during the assessment of betpotwins.web.app.

  • The request stayed on betpotwins.web.app. It was not redirected to another domain. Clear
  • It is hosted on FASTLY, a network registered in US. Noted

Domain intelligence

RegistrarNot available
HostingFASTLY - Fastly, Inc.
Network registered inUS
Server IP2620:0:890::100 (a CDN edge address; the server behind it was not observed)
Name serversNot available
CDN / edge networkDetected (fastly)
Resolved IP addresses2
Edge IP addresses2
Likely origin IP addresses0
SSL issuerWR3
SSL expiry2027-01-25
First seen (web archive)Not available (the web archive has no record of this address; a site on web.app has no registration of its own)
Domain expiryNot available
Archive first seenNot available
Archive snapshots0
ReputationVirusTotal: 0 malicious, 1 suspicious | AbuseIPDB (CDN edge address, not the host): 1% confidence, 3 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about betpotwins.web.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 betpotwins.web.app

Is betpotwins.web.app a scam?

TrustSniffer's assessment of betpotwins.web.app found strong scam indicators. It scored 5 out of 100 on 2026-11-13, which is the critical-risk band. The specific signals are listed in the evidence above.

Is betpotwins.web.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 betpotwins.web.app?

betpotwins.web.app scored 5 out of 100 on 2026-11-13, 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-13 · how we assess · report a mistake