context safety score
A score of 23/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
Domain nregade2.nic.in mimics the legitimate Indian government NIC (National Informatics Centre) domain nic.in with a suspicious subdomain 'nregade2', potentially impersonating NREGA (National Rural Employment Guarantee Act) government services to deceive users into trusting a fraudulent site. (location: metadata.json: domain=nregade2.nic.in)
brand impersonation
The domain nregade2.nic.in combines 'nrega' (India's NREGA government scheme) and 'de2' under the nic.in namespace. While nic.in is a legitimate Indian government TLD-equivalent, the subdomain pattern 'nregade2' is anomalous and may represent an unauthorized or spoofed subdomain impersonating official NREGA digital services. (location: metadata.json: domain=nregade2.nic.in)
phishing
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) for a domain claiming to be under nic.in government infrastructure. Legitimate Indian government NIC-hosted services maintain valid TLS certificates. A failed TLS connection on a government-impersonating domain strongly indicates a malicious or compromised host serving content without proper certificate validation, consistent with a phishing operation. (location: metadata.json: tls.connected=false, tls.cert_valid=false, tls.san_match=false)
social engineering
The site targets users seeking government welfare services (NREGA employment scheme). Impersonating a government employment guarantee portal is a high-impact social engineering vector targeting vulnerable, low-income populations who may submit personal identification, bank account details, or job card numbers. (location: metadata.json: domain=nregade2.nic.in)
credential harvesting
A domain impersonating an Indian government NREGA portal with failed TLS and no verifiable certificate is a high-risk credential harvesting vector. NREGA portals typically collect Aadhaar numbers, bank account details, and job card IDs — sensitive PII that would be valuable to harvest via a spoofed government login page. (location: metadata.json: domain=nregade2.nic.in, tls=invalid)
curl https://api.brin.sh/domain/nregade2.nic.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
nregade2.nic.in currently scores 23/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.