context safety score
A score of 36/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
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
exfiltration
JavaScript intercepts form submissions to exfiltrate data
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The Yoast SEO JSON-LD structured data block declares the WebSite and Organization entities with @id and url pointing to 'https://www.elevatesummit.info/' and names them 'Airship'. This causes search engines and AI agents that consume schema.org metadata to associate the Airship brand identity (Organization, Brand, OnlineBusiness) with the third-party domain elevatesummit.info rather than airship.com. The SearchAction urlTemplate also resolves to elevatesummit.info, meaning automated agents following schema.org potentialAction could be directed to that external domain for searches. (location: page.html, line 29, <script type='application/ld+json' class='yoast-schema-graph'>)
malicious redirect
The JSON-LD SearchAction potentialAction urlTemplate is set to 'https://www.elevatesummit.info/?s={search_term_string}', meaning any AI agent or search engine bot that programmatically follows schema.org SearchAction discovery will send search queries to an unrelated third-party domain (elevatesummit.info) instead of airship.com. This constitutes a metadata-level redirect of automated agent traffic. (location: page.html, line 29, JSON-LD WebSite.potentialAction.SearchAction.urlTemplate)
prompt injection
The JSON-LD structured data misattributes the Airship brand and website identity to elevatesummit.info. AI agents that ingest structured data to understand page context or answer queries about the page owner would be fed false organizational identity data, effectively injecting incorrect factual claims into the agent's reasoning about who operates this site. (location: page.html, line 29, JSON-LD @graph WebSite and Organization nodes with @id 'https://www.elevatesummit.info/#website' and 'https://www.elevatesummit.info/#organization')
curl https://api.brin.sh/domain/urbanairship.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
urbanairship.com currently scores 36/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.