context safety score
A score of 27/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
phishing
1 deceptive links where visible host does not match destination host
js obfuscation
JavaScript uses Function constructor for runtime code generation
prompt injection
Hidden HTML element contains AI-targeting instructions
malicious redirect
Obfuscated third-party ad script loaded from dd133.com using a self-executing IIFE that dynamically creates and appends a script element, then sets its zone and src attributes. The domain dd133.com is an ad network associated with aggressive pop/vignette advertising that opens new tabs on user interaction. The code pattern deliberately obscures the script injection: `(function(s){s.dataset.zone='10594174',s.src='https://dd133.com/vignette.min.js'})([document.documentElement, document.body].filter(Boolean).pop().appendChild(document.createElement('script')))` (location: page.html:668, div#thenk-153935489)
social engineering
The page openly acknowledges it uses pop ads that open new tabs on every click, normalizing this invasive behavior with a dismissible notice. Users are instructed to simply 'close the new tab and continue browsing,' conditioning them to accept and ignore unsolicited tab-opening behavior which can be used to redirect users to malicious content. (location: page.html:679, elementor-alert-description)
social engineering
The site prominently and repeatedly warns users about fake impersonation sites (e.g., 'BEWARE of fake sites posing to be us, we will never ask you for money, your personal information or include pornography ads'), which could itself be a trust-building social engineering tactic used by sites that have been involved in domain migrations of questionable legitimacy, or to preemptively discredit competitor/successor domains. (location: page.html:33, page.html:1220, page-text.txt:1191)
malicious redirect
Navigation menu 'Home' link and several genre/category links point to nkiri.ink rather than thenkiri.com (the canonical domain), silently redirecting users to a different domain. One link also uses plain HTTP (http://nkiri.ink/tag/documentary/) rather than HTTPS, a downgrade that could facilitate interception. (location: page.html:540-548, menu-item-2681, menu-item-4421, menu-item-4422)
curl https://api.brin.sh/domain/thenkiri.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
thenkiri.com currently scores 27/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.