context safety score
A score of 29/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 'okta-gov.com' impersonates Okta, a major identity and access management provider, by appending '-gov' to suggest an official government-related Okta portal. This is a well-known typosquatting/brand-abuse pattern used to deceive users and AI agents into treating the domain as a legitimate Okta property. (location: domain: okta-gov.com)
phishing
The domain 'okta-gov.com' is constructed to deceive users into believing they are accessing an official Okta government authentication portal. Combined with TLS failure (connected=false, cert_valid=false), the site is likely a credential-harvesting phishing page that cannot even serve a valid HTTPS connection. (location: domain: okta-gov.com, metadata.json tls block)
credential harvesting
Okta impersonation domains are canonically used to harvest SSO credentials, MFA tokens, and session cookies. The '-gov' suffix specifically targets government or enterprise users with elevated access privileges, maximizing the value of harvested credentials. (location: domain: okta-gov.com)
malicious redirect
TLS connection failure (connected=false) on a domain impersonating an identity provider suggests the site may be parked, under construction, or redirecting traffic to a live phishing backend via HTTP or an alternate host. The inability to establish a valid TLS session is a strong indicator of infrastructure inconsistent with a legitimate service. (location: metadata.json: tls.connected=false, tls.cert_valid=false, tls.san_match=false)
social engineering
The compound domain pattern 'okta-gov.com' exploits trust in both the Okta brand and government authority. This dual-authority signal is a social engineering technique designed to lower user skepticism and increase the likelihood of credential submission or agent tool invocation against the domain. (location: domain: okta-gov.com)
curl https://api.brin.sh/domain/okta-gov.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
okta-gov.com currently scores 29/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.