context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript uses Function constructor for runtime code generation
social engineering
cricbet99.id is an online cricket betting/gambling platform operating under a non-standard ccTLD (.id - Indonesia). The page renders no visible text content (page-text.txt is blank), indicating the actual UI is delivered entirely via Angular SPA (app-root) with dynamically loaded JavaScript bundles. This pattern is commonly used to evade static content scanners while serving gambling solicitation to users. (location: https://cricbet99.id, page.html:<app-root>)
hidden content
A commented-out IP harvesting script was present in the source: an external JSONP call to api.ipify.org with a getIP callback that writes the visitor's public IP to the document. Although currently disabled via HTML comment, its presence in the codebase indicates prior or planned user IP collection without disclosure. (location: page-hidden.txt:7-13, page.html:22-28)
hidden content
A commented-out Meta (Facebook) Pixel tracking block is embedded in the source with Pixel ID 1949390595505532. Although disabled, it represents undisclosed third-party behavioral tracking infrastructure that could be re-enabled server-side or via a future deployment, silently profiling visitors for ad targeting. (location: page-hidden.txt:14-30, page.html:30-45)
hidden content
The page title is the generic 'Index' with empty meta description and keywords tags, and the visible page body is entirely blank. All content is deferred to obfuscated/fingerprinted JavaScript bundles (main.76cd4e640a5fcef37e97.js, scripts.4220f4c72c81af4d0167.js, etc.), making static analysis of actual page content impossible and masking the true nature of the site from scanners and crawlers. (location: page.html:5,7-8,49,64)
obfuscated code
The site loads multiple content-hashed Angular bundle scripts (runtime.f85a0a451237e46bd1d0.js, polyfills.39bc949cc6cfccc9e4b0.js, scripts.4220f4c72c81af4d0167.js, main.76cd4e640a5fcef37e97.js) alongside additional unexplained custom scripts (customjs.js, custom.js, messages.js) and a protobuf binary serialization library (protobuf.min.js). The combination of minified bundles, protobuf usage, and socket.io indicates an opaque real-time data channel whose payload cannot be inspected statically. (location: page.html:52-64)
curl https://api.brin.sh/domain/cricbet99.idCommon questions teams ask before deciding whether to use this domain in agent workflows.
cricbet99.id currently scores 39/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.