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 iqair.com renders a 'Vercel Security Checkpoint' page. iqair.com is not a Vercel product; presenting Vercel's branded checkpoint UI on a third-party domain impersonates Vercel's infrastructure brand to lend false legitimacy to a browser-verification gate. (location: page.html: <title>Vercel Security Checkpoint</title>, page-text.txt line 1)
obfuscated code
The page contains heavily obfuscated JavaScript with shuffled string arrays, integer-math integrity checks, and encoded function lookups (e.g., rotating array with parseInt puzzles, string-index accessor function `i()`/`s()`). This pattern is characteristic of anti-analysis obfuscation used to hide redirect logic, fingerprinting, or challenge-bypass code from automated scanners and human reviewers. (location: page.html line 2: <script type="module"> obfuscated block with _() and k() string arrays)
malicious redirect
The page is a JavaScript-driven interstitial ('We're verifying your browser') served at iqair.com — a well-established air-quality domain (10424-day-old domain). The real iqair.com site content is entirely absent; instead users see a scripted checkpoint that controls what page they ultimately reach. The obfuscated script dynamically manipulates the DOM and likely performs a conditional redirect based on browser fingerprint or bot-detection results, hiding the true destination from static analysis. (location: page.html lines 1-3: spinner + header-text + obfuscated module script)
social engineering
The visible text 'We're verifying your browser' and 'Enable JavaScript to continue' are classic social-engineering prompts used to pressure users into enabling JavaScript or completing CAPTCHA-like interactions, lowering their guard before delivering malicious content or redirecting them. (location: page-text.txt line 1: 'We're verifying your browser', 'Enable JavaScript to continue')
hidden content
The #root div is explicitly set to 'display:none' in CSS and the main UI is rendered only after JavaScript executes. The actual page content — including any destination URL or injected payload — is entirely hidden from non-JS crawlers and static analysis tools, a technique used to conceal malicious content from security scanners. (location: page.html line 1: #root{display:none} style rule; body depends entirely on JS execution to reveal content)
curl https://api.brin.sh/domain/iqair.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
iqair.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.