context safety score
A score of 37/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
hidden content
1 hidden or tiny iframe elements detected
cloaking
Page loads content in transparent or zero-size iframe overlay
brand impersonation
Page is served under betway.com but its entire content is a Spin Palace Casino rebrand takeover. The visible hero text reads 'BETWAY IS NOW SPIN PALACE CASINO' and the sole CTA button redirects to https://spinpalacecasino.com/us/. SEO metadata still advertises Betway trustworthiness while actual content redirects users away, creating a deliberate mismatch between indexed content and user-facing content. (location: page.html / page-text.txt: <title>Betway USA</title> vs <a href='https://spinpalacecasino.com/us/'>CONTINUE TO SPIN PALACE</a>)
malicious redirect
A hardcoded redirect button and backend configuration property 'newBrandDomain':'https://www.spinpalacecasino.com/us/' drive all users from betway.com to the external domain spinpalacecasino.com. The redirect uses target='_self' to replace the Betway-branded tab, providing no way for users to remain on Betway. The destination is a completely separate domain and brand. (location: page.html: <a target='_self' href='https://spinpalacecasino.com/us/'> and JSON payload 'newBrandDomain':'https://www.spinpalacecasino.com/us/')
social engineering
The page employs multiple psychological manipulation techniques: (1) authority framing — presents brand migration as official and inevitable; (2) false reassurance — 'A royal upgrade fit for winners!'; (3) ownership/entitlement framing — 'Your account, balance, and rewards from Betway are awaiting you'; (4) loss aversion via 'awaiting you' implying inaction means losing rewards; (5) trust transfer leveraging Betway brand equity to legitimize Spin Palace; (6) a single CTA with no opt-out or alternative navigation. (location: page-text.txt line 1: full visible page content; page.html: rebrandHero component)
hidden content
A zero-size invisible iframe loads '/ensighten-betway.html' using visibility:hidden;width:0;height:0. This iframe executes arbitrary JavaScript from an unaudited file not included in the scanned assets. Ensighten is a tag management platform capable of injecting additional scripts, trackers, or redirect logic outside the visible page. (location: page.html: <iframe style='visibility:hidden;width:0;height:0' id='ensighten' src='/ensighten-betway.html'>)
hidden content
Next.js Suspense error boundary markers (<!--$!--> and <!---/$-->) indicate portions of the page were in a failed/suspended state at capture time. Content inside failed Suspense boundaries may not have been rendered in the static snapshot, meaning additional page content — potentially including credential forms, additional redirects, or further social engineering — may load post-hydration and is not visible in the captured HTML. (location: page-hidden.txt: <!--$!--> and <!--/$--> markers)
malicious redirect
AppsFlyer OneLink URL used for mobile app redirects is explicitly labeled as an 'Upsell' retargeting campaign targeting existing Betway users: c=Upsell&is_retargeting=true. This indicates existing Betway customers are being actively re-targeted via mobile deep-links (af_dp=betway://) to migrate them to Spin Palace, confirming the commercial intent behind the brand migration funnel. (location: page.html: https://betwayus.onelink.me/joGC?af_xp=custom&pid=Website&c=Upsell&is_retargeting=true&af_dp=betway%3A%2F%2F)
obfuscated code
An unrecognized third-party script 'vtrk-min.js' is preloaded from the domain media.src-play.com — a non-prominent domain with a name suggesting visitor tracking. This script executes on page load and cannot be audited from the static HTML. It represents an unverified third-party code execution vector that could perform tracking, fingerprinting, or data exfiltration beyond what is disclosed. (location: page.html: <link rel='preload' href='https://media.src-play.com/plugins/analytics/vtrk-min.js' as='script'/>)
curl https://api.brin.sh/domain/betway.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
betway.com currently scores 37/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.