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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
brand impersonation
The domain oath.com is serving content that fully impersonates Yahoo Inc. (yahooinc.com), including Yahoo branding, logos, product listings (Yahoo Ads, Yahoo DSP, Yahoo Search), and official-looking press releases. The HTML declares data-wf-domain="www.yahooinc.com" and the page title is "Yahoo Inc." while the actual domain is oath.com — a former Verizon holding company name that is not the official Yahoo Inc. corporate domain. (location: page.html:1, metadata.json domain field)
malicious redirect
A JavaScript redirect is present that silently sends users from /our-story/diversity to /our-story without user interaction or notification. While possibly a legacy redirect, on an impersonation site this pattern can be used to hide or suppress specific content pages. (location: page.html:2-4)
hidden content
A <style> block injected at the very end of the <body> (just before </body>) embeds a large base64-encoded PNG image as a CSS cursor override. This is an anomalous placement for cursor styling — legitimate cursor CSS belongs in the <head> or a stylesheet, not appended to the body. The encoded binary blob is not human-readable and could serve as a covert data channel or payload carrier. The content is rendered invisibly to users. (location: page.html:606-608, page-text.txt:51)
social engineering
The page impersonating Yahoo Inc. on oath.com presents fully fabricated or mirrored corporate content including press releases, career listings, and investor-facing business solutions — all designed to appear as the legitimate Yahoo corporate site. This could deceive users, partners, or automated agents into trusting the domain as an authoritative Yahoo source. (location: page-text.txt:1, page.html body content)
curl https://api.brin.sh/domain/oath.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
oath.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.