Is biharbhumiplus.bihar.gov.in safe?

suspiciousmedium confidence
46/100

context safety score

A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
40
behavior
100
content
30
graph
45

4 threat patterns detected

high

brand impersonation

The domain 'biharbhumiplus.bihar.gov.in' presents an IIS Windows Server default page instead of a legitimate Bihar land records government portal. The domain mimics an official Indian government service (Bihar Bhumi Plus) but serves a generic IIS placeholder, suggesting the real site content may have been replaced or the domain is being squatted to impersonate a government service. (location: page.html:5, metadata.json:domain)

medium

malicious redirect

The page contains a link to 'http://go.microsoft.com/fwlink/?linkid=66138&clcid=0x409' embedded in an image anchor tag. While this is a standard IIS default page link, the presence of a default IIS page on a supposed government domain is anomalous and may indicate a compromised or hijacked server serving redirect infrastructure. (location: page.html:29)

high

hidden content

The TLS certificate expires in only 4 days (days_until_expiry: 4), which is critically low for an active government service. Combined with the domain serving a bare IIS default page with no actual government content, this strongly indicates the legitimate site has been taken offline, replaced, or the domain is being used as infrastructure for malicious purposes while appearing to be a government domain. (location: metadata.json:tls.days_until_expiry)

high

social engineering

The subdomain 'biharbhumiplus.bihar.gov.in' uses a '.gov.in' TLD pattern that signals an official Indian government entity, lending false legitimacy. The domain name combines 'Bihar' (Indian state) and 'Bhumi' (land/property) to impersonate the Bihar land registration/records portal, a high-value target for social engineering attacks against citizens seeking land record services. The current state of the site (IIS default page) may be a transitional state during a compromise or spoofing campaign. (location: metadata.json:domain)

API

curl https://api.brin.sh/domain/biharbhumiplus.bihar.gov.in

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is biharbhumiplus.bihar.gov.in safe for AI agents to use?

biharbhumiplus.bihar.gov.in currently scores 46/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.

How should I interpret the score and verdict?

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.

How does brin compute this domain score?

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.

What do identity, behavior, content, and graph mean for this domain?

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.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

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.

Can I rely on a safe verdict as a full security guarantee?

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.

When should I re-check before using an entity?

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.

Last Scanned

March 7, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Trust Graph

Disclaimer

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.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.