context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
The site ceouttarpradesh.nic.in failed TLS connection (connected=false, cert_valid=false, san_match=false). A government domain (nic.in is India's National Informatics Centre) that cannot establish a valid TLS session is highly anomalous — legitimate government portals maintain valid certificates. This may indicate a spoofed or compromised domain targeting citizens expecting a trusted government site. (location: metadata.json: tls fields)
brand impersonation
The domain ceouttarpradesh.nic.in uses the nic.in subdomain structure associated with official Indian government infrastructure (National Informatics Centre). However, TLS validation completely fails (connected=false, cert_valid=false, issuer=null), which is inconsistent with any legitimate nic.in property. This pattern is consistent with brand impersonation of Indian government election/voter services (CEO = Chief Electoral Officer, Uttar Pradesh). (location: metadata.json: domain, tls)
hidden content
The page.html, page-text.txt, and page-hidden.txt files are all completely empty despite the domain resolving and being scanned. This absence of content combined with TLS failure suggests the page may be serving no content intentionally (e.g., a parked impersonation domain, a redirect-only shell, or content withheld based on user-agent/IP to evade scanners). (location: page.html, page-text.txt, page-hidden.txt (all empty))
malicious redirect
The combination of an empty page body and failed TLS on a government-branded domain suggests possible use as a redirect intermediary — serving no direct content to automated scanners while redirecting human visitors (browser-based) to phishing or credential harvesting pages targeting Indian voters or government service users. (location: page.html (empty body), metadata.json: tls.connected=false)
curl https://api.brin.sh/domain/ceouttarpradesh.nic.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
ceouttarpradesh.nic.in currently scores 47/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.