context safety score
A score of 43/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 sspy-up.gov.in uses a .gov.in TLD (Indian government top-level domain) but TLS connection failed entirely (connected=false, cert_valid=false). Legitimate Indian government sites maintain valid TLS certificates. A failed TLS connection on a purported government domain strongly suggests the site may be down, misconfigured, or a spoofed/impersonation site that cannot sustain a valid certificate. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
brand impersonation
The domain sspy-up.gov.in mimics an official Indian government portal (sspy = Social Security Pension Scheme, UP = Uttar Pradesh). The .gov.in suffix is reserved for Indian government entities. Combined with TLS failure and unknown domain age and hosting reputation, this raises significant concern that the site may be impersonating or is an unverified clone of the legitimate UP government pension portal (sspy-up.gov.in is the known legitimate site, but the inability to verify TLS and unknown WHOIS age mean authenticity cannot be confirmed). (location: metadata.json: domain=sspy-up.gov.in, tls invalid, whois domain_age_days=null)
credential harvesting
The SSPY UP portal is a social security pension scheme site where citizens submit personal identification and banking details. A site impersonating or spoofing this domain with invalid TLS would be positioned to harvest Aadhaar numbers, bank account details, and other sensitive PII from beneficiaries seeking pension services. (location: metadata.json: domain=sspy-up.gov.in; site purpose inferred from domain name)
social engineering
Targeting elderly or low-income pension beneficiaries (the demographic of the UP Social Security Pension Scheme) with a site that fails TLS validation represents a high-risk social engineering vector. Victims seeking government pension services may proceed despite browser warnings due to low technical literacy, making this population especially vulnerable. (location: metadata.json: domain=sspy-up.gov.in; tls.connected=false)
curl https://api.brin.sh/domain/sspy-up.gov.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
sspy-up.gov.in currently scores 43/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.