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
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) for a domain claiming to be an official Indian government site (upsssc.gov.in). Legitimate government portals maintain valid TLS certificates. The absence of a valid certificate is a strong indicator of a spoofed or compromised site impersonating the Uttar Pradesh Subordinate Services Selection Commission. (location: metadata.json: tls.connected=false, tls.cert_valid=false, tls.san_match=false)
brand impersonation
The domain upsssc.gov.in uses a .gov.in TLD which is restricted to Indian government entities. However, TLS connection failure and unknown hosting reputation suggest this may be a site impersonating the legitimate UPSSSC government portal to deceive job seekers and citizens who interact with the official commission. (location: metadata.json: domain=upsssc.gov.in, hosting.reputation=Unknown, tls.connected=false)
credential harvesting
A government job portal with broken TLS (no encrypted connection possible) that still presents itself as an official .gov.in site poses a credential harvesting risk. Users who attempt to log in or submit personal/application data would do so over an unencrypted or unverifiable connection, exposing credentials and PII. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
curl https://api.brin.sh/domain/upsssc.gov.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
upsssc.gov.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.