context safety score
A score of 33/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page uses meta refresh redirect
malicious redirect
The page at bank.sbi (a domain impersonating State Bank of India) automatically redirects visitors to https://sbi.bank.in via a meta http-equiv refresh tag (content='5; url=https://sbi.bank.in/'). The legitimate SBI domain is www.onlinesbi.sbi or sbi.co.in — sbi.bank.in is a suspicious lookalike domain not associated with the official bank. This unsolicited redirect could route users to a credential-harvesting or phishing site. (location: page.html:6 — <meta http-equiv="refresh" content="5; url=https://sbi.bank.in/">)
brand impersonation
The page fully impersonates State Bank of India (SBI), India's largest public-sector bank, using its official logo, name, copyright notice ('© State Bank of India'), and color scheme. The domain bank.sbi is not the official SBI web presence and is being used to deceive users into trusting the redirect and the destination site sbi.bank.in. (location: page.html:172-183 — logo, heading, copyright elements)
phishing
The combination of full SBI brand impersonation, automatic redirect to a non-official domain (sbi.bank.in), and urgency messaging ('You will be automatically redirected. Please bookmark & use the new URL') constitutes a classic phishing lure. Users are socially engineered into accepting and bookmarking a fraudulent URL as their banking destination. (location: page.html:175-178 — 'Important Information' block with redirect link)
social engineering
The page fabricates an official-sounding 'migration of Corporate Website to new URL' announcement to legitimize the redirect. It instructs users to bookmark the new fraudulent URL, which would ensure persistent future access to the phishing destination. The loading spinner adds a false sense of automated legitimacy. (location: page.html:175-180 — migration announcement, bookmark instruction, spinner)
credential harvesting
The redirect destination sbi.bank.in is a lookalike domain positioned to harvest banking credentials. Users believing they are on the official SBI site are redirected and encouraged to bookmark sbi.bank.in, where login forms could capture usernames, passwords, and OTPs. The CSS comment '/* PNB red */' referencing Punjab National Bank while impersonating SBI suggests a recycled phishing template. (location: page.html:6 (redirect target) and page.html:39 (CSS comment referencing wrong bank — PNB vs SBI))
hidden content
The modal-header div containing 'State Bank of India' is commented out in the HTML but the modal itself is forcibly shown via inline style (display:flex), bypassing the CSS 'display:none' default. This pattern of toggling visibility via inline override while hiding elements in comments is characteristic of content obfuscation and evasion of automated scanners. (location: page.html:167 — inline style override; page.html:169 — commented-out modal-header)
curl https://api.brin.sh/domain/bank.sbiCommon questions teams ask before deciding whether to use this domain in agent workflows.
bank.sbi currently scores 33/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.