context safety score
A score of 35/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
brand impersonation
Domain 'businessbanking.nedsecure.co.za' impersonates Nedbank, a major South African bank, by combining 'ned' and 'secure' with 'businessbanking' to appear as a legitimate Nedbank business banking portal. The legitimate domain is nedbank.co.za; this domain is not affiliated. (location: domain: businessbanking.nedsecure.co.za)
phishing
The domain is constructed to mimic a business banking login portal (subdomain 'businessbanking', domain 'nedsecure') targeting business banking customers of Nedbank. Combined with TLS failure and empty page content, this is consistent with an active or staged phishing site. (location: url: https://businessbanking.nedsecure.co.za)
credential harvesting
A fake business banking portal impersonating Nedbank is a classic credential harvesting setup, designed to collect corporate banking usernames, passwords, and OTPs from victims who believe they are on the legitimate Nedbank business banking site. (location: url: https://businessbanking.nedsecure.co.za)
hidden content
Page HTML and visible text are completely empty despite the domain being live and resolving. This is consistent with content that is only rendered dynamically, served after a redirect, or deliberately hidden from automated scanners — a common evasion technique used by phishing kits. (location: page.html, page-text.txt, page-hidden.txt (all empty))
malicious redirect
The combination of an empty page body and a failed TLS connection suggests the site may serve a redirect or JavaScript-based forwarding to a phishing payload only under specific conditions (e.g., user-agent, referrer, geolocation), evading automated content analysis. (location: url: https://businessbanking.nedsecure.co.za)
social engineering
The full URL 'https://businessbanking.nedsecure.co.za' is crafted to appear trustworthy to business banking customers: 'businessbanking' implies legitimacy, 'nedsecure' suggests a security-focused Nedbank subdomain. This linguistic construction is designed to lower victim suspicion and induce credential submission. (location: domain: businessbanking.nedsecure.co.za)
curl https://api.brin.sh/domain/businessbanking.nedsecure.co.zaCommon questions teams ask before deciding whether to use this domain in agent workflows.
businessbanking.nedsecure.co.za currently scores 35/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.