context safety score
A score of 30/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
malicious redirect
script/meta redirect patterns detected in page source
malicious redirect
The page immediately redirects all visitors via JavaScript (window.location.href) to 'https://4rabet120.com/?show_reg=true', a different domain with a registration prompt. The source domain join4ra.com serves purely as a redirect intermediary, concealing the true destination from users and security filters. (location: page.html:16)
hidden content
A hidden clickable element is embedded at the top of the page (position:absolute, opacity:0, 5x5px, z-index:1000) containing an anchor tag linking to '/api/bbonus.php?sub_id1=bb25' with an image labeled 'GET MAIN BONUS!'. This invisible affiliate/tracking trap could capture clicks or register affiliate conversions without user awareness. (location: page.html:10-14)
social engineering
The redirect destination URL includes the parameter '?show_reg=true', which automatically triggers a registration modal or flow on arrival, pressuring visitors into signing up for a gambling service (4rabet) immediately upon landing, with no informed consent from the user. (location: page.html:16)
brand impersonation
The page title is '4RAbet' and redirects to '4rabet120.com', using a numeric suffix ('120') appended to the brand name '4rabet'. This pattern is commonly used to create lookalike domains that impersonate or proxy a known gambling brand, potentially for unauthorized affiliate traffic routing or phishing. (location: page.html:5, page.html:16)
phishing
The TLS certificate expires in only 3 days (days_until_expiry: 3), which is characteristic of short-lived certificates used in phishing infrastructure to evade long-term blocklisting. Combined with the immediate redirect to a registration page, this raises phishing risk for credential harvesting on the destination site. (location: metadata.json:1)
curl https://api.brin.sh/domain/join4ra.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
join4ra.com currently scores 30/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.