context safety score
A score of 32/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
brand impersonation
Domain 'myaadhaaruidai.com' mimics the official Indian government Aadhaar identity authority (uidai.gov.in) by combining 'aadhaar' and 'uidai' into a single unofficial domain. This is a textbook lookalike/typosquat targeting citizens seeking government identity services. (location: domain: myaadhaaruidai.com)
phishing
The domain impersonates India's UIDAI Aadhaar government identity platform, a high-value phishing target used to harvest national ID numbers, biometrics, and personal information from citizens. (location: domain: myaadhaaruidai.com)
malicious redirect
The root page contains only a JavaScript redirect via 'window.location.href="/lander"' with no visible content. This technique hides the actual phishing lander from scanners and bots while redirecting human visitors to a credential-harvesting page. (location: page.html:1 — window.onload script)
hidden content
The page renders no visible text content (page-text.txt is empty) while using a JavaScript-only redirect. This cloaking technique deliberately hides the true purpose of the page from automated crawlers and content analysis tools. (location: page.html:1 — empty body with JS-only redirect)
credential harvesting
The combination of UIDAI/Aadhaar impersonation, a JS redirect to '/lander', and completely empty visible content is a strong indicator of a credential-harvesting operation targeting Aadhaar card numbers, OTPs, and personally identifiable information of Indian residents. (location: domain: myaadhaaruidai.com; redirect target: /lander)
curl https://api.brin.sh/domain/myaadhaaruidai.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
myaadhaaruidai.com currently scores 32/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.