context safety score
A score of 46/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
malicious redirect
script/meta redirect patterns detected in page source
malicious redirect
Session storage redirect: the page executes `window.sessionStorage.getItem('xl')` and immediately redirects the browser to whatever URL is stored under the key 'xl'. This is a client-side open redirect that can silently send visitors (including AI agents following links) to an attacker-controlled URL with no visible indication in the page markup. (location: page.html:72 — <script>window.sessionStorage.getItem("xl")&&(window.location.href=window.sessionStorage.getItem("xl"));</script>)
malicious redirect
Third-party pop/redirect ad network script loaded from 'acscdn.com' via protocol-relative URL (//acscdn.com/script/aclib.js) with zone ID 9008714. The aclib.runPop() call triggers pop-under or forced redirect ads, which can redirect users to phishing, malware, or scam pages without user consent. (location: page.html:77-81 — aclib.runPop({zoneId:'9008714'}))
malicious redirect
Third-party script dynamically injected from 'scripts.cleverwebserver.com' (CleverCoreLoader98023). This ad/redirect network script inserts itself at the top of the DOM and can initiate forced redirects or pop-unders. The placeholder callback attributes ('put-your-callback-function-here', 'put-your-click-macro-here') indicate an incompletely configured but live ad redirector deployment. (location: page.html:116 and page.html:119-144 — AdsCoreLoader97889 (sads.adsboosters.xyz) and CleverCoreLoader98023 (scripts.cleverwebserver.com))
malicious redirect
Additional third-party ad script loaded from 'sads.adsboosters.xyz' (AdsCoreLoader97889). The domain name pattern ('adsboosters') and use of a hashed JS filename suggest a low-reputation ad network capable of initiating drive-by redirects or malvertising. (location: page.html:116 — <script src="https://sads.adsboosters.xyz/f3f5d15da01751f481e68eac499a902d.js">)
social engineering
Header CTA button prominently prompts visitors to 'Join us on Telegram' (https://t.me/carnewszz), directing users off-site to a Telegram channel. Telegram channels are commonly used for follow-on social engineering, scam promotions, and phishing link distribution outside the browser's security context. (location: page.html:179-183 — <a href="https://t.me/carnewszz" class="ct-button" aria-label="Join us on Telegram">)
curl https://api.brin.sh/domain/carnewz.siteCommon questions teams ask before deciding whether to use this domain in agent workflows.
carnewz.site currently scores 46/100 with a suspicious verdict and medium 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.