context safety score
A score of 37/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
The page is served from mb66a3.com but the canonical URL, structured data @id, and all internal links point to mb669e.vip. The page also references mb66e.top in the title/meta tags. This multi-domain redirect network (mb66a3.com -> mb66e.top / mb669e.vip) is a classic cloaking and traffic-laundering pattern used by unlicensed gambling operations to evade blocklists. (location: <link rel='canonical' href='https://mb66e.top/'> and schema.org @id: https://mb669e.vip/gamelobby/live)
social engineering
The site is an unlicensed online casino/gambling platform targeting Vietnamese users. It promotes financial transactions (Bank, USDT, Momo Pay, Zalo Pay) and solicits user registration and login, with persuasive urgency language ('Đăng ký, đăng nhập ngay'). The FAQ falsely claims legal licenses from Isle of Man and Cagayan Freeport to build false trust. (location: metadata.json, page.html <meta name='description'>, FAQ schema.org structured data)
credential harvesting
The page solicits user registration and login (Đăng Ký / Đăng Nhập) while the actual serving domain (mb66a3.com) differs from the canonical domain (mb66e.top) and schema domain (mb669e.vip). Credentials entered may be captured by the serving domain before any redirect, constituting a credential harvesting risk. (location: BreadcrumbList schema items: https://mb669e.vip/#Login and https://mb669e.vip/#Register)
hidden content
The page-text.txt contains only a JavaScript loading overlay call, indicating the page's visible content is entirely JavaScript-rendered and not present in the raw HTML body. All meaningful content (casino offers, login/register forms, promotions) is loaded dynamically from external scripts hosted on q7sm4r.katawee.net, hiding the true content from static scanners. (location: page-text.txt line 1; page.html <body> containing only JsLoadingOverlay.show(...))
obfuscated code
All application logic is loaded from an external third-party CDN (q7sm4r.katawee.net) via multiple bundle scripts (preload.bundle.js, vendor.bundle.js, main.bundle.js) under a path that includes a seemingly random hash (6ca1dc292f). This pattern obscures the true behavior of the page and prevents static analysis of the actual gambling/credential-collection functionality. (location: page.html: <script src='https://q7sm4r.katawee.net/system-requirement/Web.PortalNew/UK262-01/6ca1dc292f/preload.bundle.js'>)
brand impersonation
The site uses the 'MB66' brand across multiple lookalike domains (mb66a3.com, mb66e.top, mb669e.vip, mb6661.net, appmb66.shop) to create a network of sites that mutually reinforce brand legitimacy. The schema.org structured data uses fake aggregate ratings (4.8 stars, 254 reviews) to fabricate credibility for an unverified gambling entity. (location: page.html schema.org Casino aggregateRating block; og:image from mb6661.net; FAQ downloadUrl appmb66.shop)
social engineering
A local script /js/ssodeestsebo.js with an obfuscated/meaningless filename is loaded before any other script, suggesting it may perform fingerprinting, cookie manipulation, or SSO token harvesting prior to loading the main application bundles. (location: page.html: <script src='/js/ssodeestsebo.js?single'>)
curl https://api.brin.sh/domain/mb66a3.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
mb66a3.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.