context safety score
A score of 40/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
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The scanned domain is 'the-independent.com' but the legitimate publication operates at 'independent.co.uk'. The page fully clones The Independent's branding, masthead, navigation, and content structure. Open Graph metadata references 'independent.co.uk' assets (og:image, twitter:image point to https://www.independent.co.uk/img/shortcut-icons/icon-96x96.png) while the serving domain is different, indicating a copycat/typosquat site impersonating a major UK/US news outlet. (location: metadata.json domain field, page.html og:image and twitter:image meta tags, page.html og:url set to https://www.the-independent.com/)
malicious redirect
The TLS certificate expires in only 19 days (days_until_expiry: 19), which is atypically short for a legitimate long-running news site. Short-lived certificates are a common characteristic of phishing and impersonation infrastructure that is frequently rotated. Combined with the domain mismatch from independent.co.uk, this raises concern about transient malicious infrastructure. (location: metadata.json tls.days_until_expiry)
brand impersonation
The page sources images and icons directly from 'independent.co.uk' (the legitimate site) via absolute URLs, while serving content from 'the-independent.com'. This cross-domain asset hotlinking is a hallmark technique of impersonation sites to appear visually identical to the legitimate brand without hosting those assets themselves. (location: page.html meta og:image='https://www.independent.co.uk/img/shortcut-icons/icon-96x96.png', twitter:image same value)
social engineering
The site presents a push-notification consent prompt ('Stay up to date with notifications from The Independent') that impersonates the legitimate Independent brand. If accepted on a spoofed domain, this grants the attacker persistent browser notification access to deliver phishing messages or malicious content to users who believe they subscribed to a reputable news source. (location: page.html notification-prompt div, page-text.txt line 3)
curl https://api.brin.sh/domain/the-independent.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
the-independent.com currently scores 40/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.