Is based-bet.pages.dev a scam? TrustSniffer's high-risk assessment: 5/100

based-bet.pages.dev
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.

5 OUT OF 100
Critical Risk

based-bet.pages.dev shows high-risk / scam indicators.

Sensitive Interaction Risk Governance Risk

Assessed 2026-10-26 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 engines6 flagged itVirusTotalRisk
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the host0% confidenceAbuseIPDB, 0 reports; shared hosting inflates reportsClear
Domain age2.1 years oldRegistered historyClear
Web archiveArchived since 202413 snapshotsClear
CertificateEncrypted connectionIssued by WE1Noted

The page as captured

https://based-bet.pages.dev/
Screenshot of the based-bet.pages.dev homepage captured during the TrustSniffer assessment
What based-bet.pages.dev served when TrustSniffer captured it on 2026-10-26. The page may look different now.

Key findings

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

Full analysis

Security Alert

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

The website at this address is a page hosted on a free developer-hosting subdomain. Its name suggests a betting-related service. When analysed, the page returned an interstitial from the hosting platform's security layer titled "Suspected Phishing" instead of site content. No products, offers or business model could be read from the site itself. Its apparent purpose is therefore unconfirmed, and the only observable presentation to a visitor is a security warning.

Scam/Impersonation Risk

The most serious finding is the site's standing with external threat intelligence. Several independent engines, including a tier-one security vendor, classify the address as malicious or suspicious, and the domain is blacklisted on that basis. The page a visitor reaches is itself a platform warning that the site is suspected of phishing. These signals converge and are decisive. They outweigh the clean behavioural checks in the browser sandbox. In those checks the page ran no wallet-connection routines, clipboard manipulation, hidden forms or credential posts to outside parties. The session was also not cloaked, and the content differences seen after interaction came from the bot-protection challenge. No brand impersonation or conflicting legal identities were observed. The risk therefore rests on the blacklist and warning signals, not on contradictory identity claims. The page also produced heavy third-party traffic, which is analysed under verification. The operator's real-world identity has not been independently established, so any claim of legitimacy would be unsupported.

Evidence
  • Homepage: the retrieved page was a platform interstitial titled "Suspected Phishing", served with an access-denied status instead of normal site content.
  • Reputation: six engines rated the address malicious and two suspicious, including one tier-one security vendor, and the external blacklist check is positive.
  • Domain provenance: the domain is about 2.1 years old, with 13 archive snapshots spanning 2024–2025 (2 years tracked). That history is continuous but thin, and it gives no basis for presuming legitimacy.

Regulatory Verification Notes

No legal, terms, about or licensing page could be assessed, because the only content retrieved was the warning interstitial. No gambling, financial-services or other licence is therefore confirmed or referenced, and the site cannot be tied to any registered operator. No third-party broker record was matched. This is a verification limitation and not evidence of wrongdoing in itself. The site's transport encryption is valid, but it is only domain-validated. That shows control of the hostname, not the identity or legitimacy of the operator, and it does not offset the reputation findings.

Evidence
  • Transport encryption: the TLS certificate is issued by WE1 (DV) and valid to 2027-01-20.
  • Hosting: served from AS13335 (Cloudflare, Inc., US).
  • Legal pages: no terms, privacy, about or licensing content was retrievable, so no licence or registration claim exists to check.

What to Verify Next

Any evaluation should treat the site as unvetted until the platform warning and the threat listings are resolved. If a business relationship is nonetheless being considered, the operator should be asked to name the legal entity behind the service and to state which gambling or financial licence it claims. Both answers should be checked in the relevant regulator's public register, using contact details taken from an independent source and not from the site. Separately, the heavy volume of third-party calls the page makes should be mapped by a security team in an isolated environment. That would show where data is sent before any interaction is considered.

Evidence
  • Browser behaviour: the page made 87 external fetch requests and 5 external POST requests across three runs. Up to 97% of traffic in a run was external, and about 1,500 page mutations followed interaction.
  • Stability: seven console errors were recorded, which is consistent with an unfinished or obstructed page.
  • Challenge handling: the page sat behind a bot challenge, so the real content was not directly observed.

Summary Verdict

The site presents an elevated, clearly cautionary risk posture. Active third-party threat detections and a platform phishing warning dominate the assessment, and nothing in the observable evidence, including a valid certificate and clean sandbox behaviour, is strong enough to counter them. The operator is unidentified and the site's real purpose cannot be established from what was retrievable.

Infrastructure Integrity

The site is delivered through Cloudflare's CDN and WAF, and all observed addresses are CDN edge servers. The origin server was not observable, so hosting cannot be verified independently. The edge network is reputable and carries no abuse reports. That is a mitigating factor only. It shows the platform is sound, not that this particular site is, and it cannot offset the external threat detections.

Closing Assessment

The site should be treated as unsafe for any sensitive interaction. No login, credential entry, wallet connection or payment should be attempted. Any viewing should be limited to a non-authenticated, isolated session, until the threat listings and the platform warning are formally cleared.

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

What the analysis found

4 findings contributed to this verdict, raised by governance, external reputation, behaviour in a sandbox, registration and ownership.

01 Governance

  • A threat feed lists this domain as malicious, and that caps the score whatever the other checks found.Governance rule:GOV_CRITICAL_BLACKLIST

02 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

03 Behaviour in a sandbox

  • Most of what the page loaded came from other domains rather than from this one.Behaviour in a sandbox rule:BEHAV_EXTERNAL_RATIO_HIGH
  • The structure of the page changed sharply while it was loading.Behaviour in a sandbox rule:BEHAV_DOM_DENSITY_SPIKE
  • The page made many background requests to other domains while it was open.Behaviour in a sandbox rule:BEHAV_EXTERNAL_XHR_HEAVY

04 Registration and ownership

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

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 based-bet.pages.dev.

  • The request stayed on based-bet.pages.dev. It was not redirected to another domain. Clear
  • The earliest public archive of this site is from 2024-09-12. Clear
  • It is hosted on CLOUDFLARENET, from a server in US. Noted

Domain intelligence

RegistrarNot available
HostingCLOUDFLARENET - Cloudflare, Inc., US
CountryUS
Server IP2606:4700:310c::ac42:2f62
Name serversNot available
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerWE1
SSL expiry2027-01-20
Domain age2.12 years (continuous registration)
Domain expiryNot available
Archive first seen2024-09-12
Archive snapshots13
ReputationVirusTotal: 6 flagged | AbuseIPDB: 0% confidence, 0 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about based-bet.pages.dev 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 based-bet.pages.dev

Is based-bet.pages.dev a scam?

TrustSniffer's assessment of based-bet.pages.dev found strong scam indicators. It scored 5 out of 100 on 2026-10-26, which is the critical-risk band. The specific signals are listed in the evidence above.

Is based-bet.pages.dev 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 based-bet.pages.dev?

based-bet.pages.dev scored 5 out of 100 on 2026-10-26, 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-26 · how we assess · report a mistake