context safety score
A score of 42/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
hidden content
The page contains a large hidden div (display:none) with hundreds of hyperlinks all pointing to https://diskominfo.sitarokab.go.id/ using explicit adult/pornographic and illegal content anchor texts (bokep, porno, xxx, child porn, pedofil, rape porn, etc.). This is a classic SEO link injection / black-hat SEO attack injected into the legitimate Kenyan government site tsc.go.ke. The hidden block appears twice in the page, spanning lines 1108-1509 in page.html and is confirmed in page-text.txt lines 597-996. (location: page.html:1108-1509, page-text.txt:597-996)
malicious redirect
All injected hidden links redirect to https://diskominfo.sitarokab.go.id/ — an external Indonesian government-spoofing domain used to boost the SEO ranking of a third-party site by piggy-backing on the authority of the legitimate tsc.go.ke domain. This constitutes unauthorized outbound link injection directing crawlers and agents to an external malicious destination. (location: page.html:1109-1508 (href=https://diskominfo.sitarokab.go.id/ on every injected anchor))
prompt injection
The injected hidden content block contains the term 'phising' (Indonesian spelling of phishing) as an anchor text linking to the external domain, alongside terms like 'situs penipu' (scam site), 'penipuan' (fraud), and 'pemerasan' (extortion). An AI agent crawling or summarizing this page would ingest these keywords and the associated malicious domain, potentially influencing downstream decisions or taint analysis pipelines with fraudulent/illegal signals originating from a trusted .go.ke government domain. (location: page.html:1300, page-text.txt:788)
hidden content
A <script> tag outside the </html> closing tag (line 1107) contains invalid inline JavaScript: 'google-site-verification=KAA2UPiU7jHOzLic510ZPyAwbl61XijiwfjMSKJdxME'. This is not valid JS and indicates tampered/injected markup placed after the document close, consistent with a site compromise where attackers appended content below the legitimate page end. (location: page.html:1107)
hidden content
The injected link block is wrapped in <div style="display:none;"> making it invisible to human visitors but fully readable by search engine crawlers, AI agents, and automated scanners. The block is duplicated (appears twice), amplifying its SEO impact and the surface area for content injection. (location: page.html:1108, page-text.txt:597)
curl https://api.brin.sh/domain/tsc.go.keCommon questions teams ask before deciding whether to use this domain in agent workflows.
tsc.go.ke currently scores 42/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.