context safety score
A score of 43/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The page at blueorigin.com (a well-known aerospace company) is serving a 'Vercel Security Checkpoint' page with title 'Vercel Security Checkpoint' and spinner UI. This is not the legitimate Blue Origin website. The actual Blue Origin content has been replaced entirely by a fake browser-verification interstitial that impersonates Vercel's security infrastructure, deceiving visitors into thinking they are interacting with a legitimate checkpoint while on the Blue Origin domain. (location: page.html:<title>, page-text.txt:line 1)
social engineering
The page displays 'We're verifying your browser' and 'Enable JavaScript to continue' — classic social engineering patterns used to coerce users into enabling JavaScript or completing fake CAPTCHA-style challenges. This technique is commonly used in phishing chains to fingerprint victims or gate malicious payloads behind a perceived legitimacy barrier. (location: page.html:body, page-text.txt:line 1)
obfuscated code
The page contains heavily obfuscated JavaScript using numeric string-array rotation (anti-deobfuscation pattern), encoded function names resolved at runtime via lookup tables, and self-defending code (anti-tampering via C() self-check using regex on function toString). The obfuscation pattern matches known malicious bot-gate and credential-harvesting interstitial frameworks. Functions build DOM element IDs character-by-character from an encoded array to evade static analysis. (location: page.html:line 2 (<script type='module'>))
malicious redirect
The obfuscated JavaScript dynamically manipulates the DOM and controls page flow entirely via runtime-decoded logic. The visible 'fix-container' link points to 'https://vercel.link/security-checkpoint' with target='_blank', but the actual navigation behavior is controlled by the obfuscated script which may redirect users to attacker-controlled destinations after completing the fake verification. The real destination of the JS-driven redirect cannot be determined without executing the obfuscated code. (location: page.html:line 3 (fix-text anchor), page.html:line 2 (obfuscated script))
phishing
A legitimate aerospace company domain (blueorigin.com, 9416 days old, OV-cert, not blocklisted) is serving a fake browser-verification interstitial instead of actual content. This is consistent with a compromised or hijacked domain being used as a phishing staging page — leveraging the domain's age and reputation to bypass security filters while presenting a fake checkpoint to harvest user interactions or deliver payloads. (location: metadata.json, page.html, page-text.txt)
curl https://api.brin.sh/domain/blueorigin.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
blueorigin.com currently scores 43/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.