context safety score
A score of 79/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
malicious redirect
The page contains a Cloudflare challenge interstitial (managed challenge) that redirects the browser via a meta refresh (content='360') and JavaScript. The cZone value 'careers.asrt.org' differs from the accessed domain 'asrt.careerwebsite.com', indicating the actual content is hosted on a different origin. While this is consistent with a legitimate Cloudflare-proxied site, the domain mismatch between the subdomain used (asrt.careerwebsite.com) and the declared zone (careers.asrt.org) warrants attention as it could be used to obscure the true destination. (location: page.html: <meta http-equiv='refresh' content='360'> and window._cf_chl_opt cZone field)
brand impersonation
The domain 'asrt.careerwebsite.com' appears to impersonate a career portal for 'ASRT' (likely the American Society of Radiologic Technologists or a similar organization), using a generic third-party domain 'careerwebsite.com' rather than the official organization domain. The Cloudflare challenge zone references 'careers.asrt.org', suggesting the legitimate site is at asrt.org, while traffic is being served from the unaffiliated 'careerwebsite.com' domain. This pattern is commonly used in phishing and credential harvesting campaigns targeting job seekers. (location: metadata.json: domain=asrt.careerwebsite.com vs page.html: cZone='careers.asrt.org')
hidden content
Seven suspicious base64 blobs were flagged by Tier 2 heuristics. The page HTML contains multiple base64-encoded data URIs embedded in CSS (e.g., an SVG icon in the #challenge-error-text background-image). These are consistent with standard Cloudflare challenge page assets and do not appear malicious, but the presence of 7 flagged blobs exceeds what is visible in the truncated HTML and warrants verification of the full source. (location: page.html: style block, #challenge-error-text background-image data:image/svg+xml;base64 URI)
social engineering
The Cloudflare challenge page instructs users to 'Enable JavaScript and cookies to continue', which is a standard browser check but can also be leveraged as a social engineering vector to coerce users into enabling features that expose them to further exploitation. In the context of a potentially impersonating domain (asrt.careerwebsite.com vs careers.asrt.org), this prompt may be used to manipulate job seekers into complying with requirements before being redirected to a credential harvesting page. (location: page.html / page-text.txt: noscript element, id='challenge-error-text')
curl https://api.brin.sh/domain/asrt.careerwebsite.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
asrt.careerwebsite.com currently scores 79/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.