context safety score
A score of 27/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
cloaking
page appears to serve substantially different content by user-agent
cloaking
Page conditionally redirects based on referrer or user-agent
exfiltration
JavaScript intercepts form submissions to exfiltrate data
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The domain google.com.bh is impersonating Google by serving what appears to be a full replica of the Google homepage (google.com), including the Google logo, search interface, Gmail/Images links, Sign In button, and Google branding. The domain is a country-code TLD (Bahrain .bh) masquerading as the legitimate google.com domain. (location: https://google.com.bh (domain level and full page content))
phishing
The page presents a convincing clone of the Google homepage with a functional Sign In link pointing to accounts.google.com, a search form with Google branding, and all standard Google UI elements. Users navigating to google.com.bh may believe they are on the legitimate Google site and submit credentials or interact with forms expecting Google's security guarantees. (location: page.html: Sign in link href='https://accounts.google.com/ServiceLogin?...' and search form)
social engineering
The page replicates Google's visual identity, layout, and interactive elements (Gmail, Images, Google apps grid, Advertising, Business Solutions, About Google footer links) to create a false sense of legitimacy, potentially deceiving users into trusting the site as an official Google property. (location: page.html: full page layout, page-text.txt lines 4-5)
curl https://api.brin.sh/domain/google.com.bhCommon questions teams ask before deciding whether to use this domain in agent workflows.
google.com.bh currently scores 27/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.