context safety score
A score of 46/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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
brand impersonation
The URL being scanned is verizonmedia.com, but the page presents itself entirely as Yahoo Inc. (title 'Yahoo Inc.', data-wf-domain='www.yahooinc.com', schema.org Organization name 'Yahoo Inc'). Verizon Media was rebranded to Yahoo in 2021; however, verizonmedia.com redirecting to/serving Yahoo Inc. content means the domain name no longer matches the brand identity displayed, creating brand confusion that could be exploited for impersonation of either Verizon or Yahoo. (location: page.html:1 - <title>Yahoo Inc.</title>, metadata.json domain: verizonmedia.com)
hidden content
A <style> block injected just before </body> contains a base64-encoded PNG data URI used as a CSS cursor value. The embedded image is non-trivial in size (~2KB base64) and is placed inline in a style tag rather than referenced via a file. While cursor overriding is sometimes legitimate, embedding opaque binary blobs as data URIs in late-page style blocks is a known technique for hiding payloads or tracking pixels from superficial HTML inspection. (location: page.html:606-608, page-text.txt:51)
hidden content
JavaScript source code (jQuery DOM manipulation, form submission handlers, IE detection logic) is visible in the extracted page-text.txt, indicating that script content was not properly separated from visible text during extraction. This suggests scripts may be executing in contexts where text content is expected, though this appears to be a Webflow rendering artifact rather than deliberate obfuscation. (location: page-text.txt:18-47)
malicious redirect
An inline script unconditionally redirects users from '/our-story/diversity' to '/our-story', silently removing access to diversity-related content. While likely a benign content management decision, it demonstrates client-side redirect logic that could be modified to redirect to arbitrary external URLs. (location: page.html:2-4)
curl https://api.brin.sh/domain/verizonmedia.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
verizonmedia.com currently scores 46/100 with a suspicious 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.