Is onlinebssc.com safe?

suspiciouslow confidence
36/100

context safety score

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

identity
80
behavior
80
content
0
graph
30

7 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

brand impersonation

The site onlinebssc.com impersonates the official Bihar Staff Selection Commission (BSSC). The legitimate government portal is bssc.bihar.gov.in. This domain uses 'onlinebssc.com' — a non-government TLD — to mimic the official BSSC branding, logo (bssc-logo.png), name, and address, deceiving job applicants into submitting applications and personal data to a non-government server. (location: page.html:126-130, metadata.json (domain: onlinebssc.com))

high

credential harvesting

The site solicits online job applications (personal data, documents, roll numbers, dates of birth) from government exam candidates under the guise of an official government portal. Candidate data submissions and document uploads (photos, certificates) are directed to onlinebssc.com infrastructure rather than the official bssc.bihar.gov.in government servers. (location: page.html:317-319, page-text.txt:449 (Login with Roll No. and Date of Birth), multiple application form links throughout)

high

social engineering

The site displays threatening legal notices in Hindi warning users that 'any tampering with this website will result in necessary legal action' and that 'information related to all users is being stored' — repeated in both the marquee notice board and footer. This intimidation tactic pressures visitors to comply and not question the site's legitimacy, a classic social engineering technique to suppress skepticism. (location: page.html:174 (marquee), page.html:1094 (footer), page-text.txt:77, page-text.txt:997)

medium

hidden content

JavaScript blocks all standard browser developer tools: F12 (keyCode 123), Ctrl+Shift+I (DevTools), Ctrl+Shift+J (Console), Ctrl+U (View Source), and Ctrl+Shift+C (Inspect Element). This anti-analysis code is designed to prevent users and security researchers from inspecting the page, a common technique used in phishing and credential-harvesting sites to evade detection. (location: page.html:60-92)

high

phishing

The domain onlinebssc.com is a lookalike/typosquat of the official bssc.bihar.gov.in government portal. It replicates the official BSSC portal's appearance to harvest job application data from Bihar government exam candidates. The site collects applications, admit card downloads, and document uploads targeting a large population of public service job seekers. (location: metadata.json (url: https://onlinebssc.com), page.html:8 (title: Welcome to Bihar Staff Selection Commission Home Page))

medium

malicious redirect

The footer and page expose a public-facing IP address (34.96.45.241) — a Google Cloud IP — rather than a government network address. Several links point to www.onlinebssc.com subpaths and cdn.onlinebssc.com for document downloads, routing sensitive government exam documents through non-government infrastructure. One link uses plain HTTP (not HTTPS): http://www.onlinebssc.com/bscmines/awscdn/notice/bscmines-advt.pdf (location: page.html:930, page.html:990 (http:// links), page.html:1100 (IP: 34.96.45.241), page-text.txt:1003)

API

curl https://api.brin.sh/domain/onlinebssc.com

FAQ: how to interpret this assessment

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

Is onlinebssc.com safe for AI agents to use?

onlinebssc.com currently scores 36/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.

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 4, 2026

Verdict Scale

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

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.