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 domain nregastrep.nic.in fails TLS connection entirely (connected=false, cert_valid=false). A legitimate Indian government NIC (National Informatics Centre) subdomain under nic.in would have a valid, trusted TLS certificate. The inability to establish a TLS connection is a strong indicator this may be a spoofed or compromised government domain, or a phishing infrastructure mimicking an official NREGA (Mahatma Gandhi National Rural Employment Guarantee Act) portal. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
brand impersonation
The subdomain nregastrep.nic.in uses the 'nic.in' government domain pattern associated with India's National Informatics Centre, specifically referencing 'nrega' (NREGA scheme) and 'strep' (possibly 'state report'). However, TLS is completely broken and no page content was retrievable, which is inconsistent with a genuine operational government portal. This pattern is consistent with domain squatting or impersonation of official Indian government digital infrastructure targeting citizens or AI agents processing government service requests. (location: metadata.json: domain=nregastrep.nic.in, tls fields)
social engineering
The domain targets NREGA (a major rural employment welfare scheme in India), a program whose beneficiaries are often low-income rural workers with limited digital literacy. Impersonating an NREGA reporting portal could be used to harvest Aadhaar numbers, bank account details, or job card information from vulnerable populations. The non-functional TLS and absence of any retrievable content suggests the site may be under construction for malicious use or actively blocking automated scanners. (location: metadata.json: domain=nregastrep.nic.in)
curl https://api.brin.sh/domain/nregastrep.nic.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
nregastrep.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.