context safety score
A score of 77/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
malicious redirect
The page is a Cloudflare challenge interstitial for 'www.legacy.com' (cZone: 'www.legacy.com') but is being served from 'announcements.shieldsgazette.com'. The JS redirects the browser URL to '/uk/obituaries/shieldsgazette-uk/browse' on legacy.com via history.replaceState and dynamically loads a Cloudflare challenge script from '/cdn-cgi/challenge-platform/...'. The cZone mismatch between the serving domain (shieldsgazette.com) and the challenge zone (www.legacy.com) indicates the page is proxying or impersonating a Cloudflare challenge for a different domain, which could be used to intercept browser state or tokens. (location: page.html: <script> block, window._cf_chl_opt.cZone = 'www.legacy.com')
brand impersonation
The URL is 'announcements.shieldsgazette.com' but the Cloudflare challenge zone is configured for 'www.legacy.com' and the challenge token URLs point to '/uk/obituaries/shieldsgazette-uk/browse' — referencing both the Shields Gazette (a UK newspaper) brand and Legacy.com (an obituaries platform). The subdomain 'announcements.shieldsgazette.com' appears to be impersonating or abusing the legitimate Shields Gazette brand to proxy Legacy.com obituary content, potentially to harvest traffic or manipulate users expecting legitimate news announcements. (location: metadata.json: domain=announcements.shieldsgazette.com; page.html: cZone='www.legacy.com', cUPMDTk='/uk/obituaries/shieldsgazette-uk/browse')
malicious redirect
The page contains a meta http-equiv refresh tag set to 360 seconds, causing an automatic page reload. While not immediately malicious on its own, combined with the domain/zone mismatch it can be used to keep users on the challenge page or re-serve the interstitial repeatedly. (location: page.html: <meta http-equiv="refresh" content="360">)
curl https://api.brin.sh/domain/announcements.shieldsgazette.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
announcements.shieldsgazette.com currently scores 77/100 with a caution 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.