context safety score
A score of 31/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
The domain auth0.net impersonates Auth0 (auth0.com), a widely trusted identity and authentication platform owned by Okta. Using the .net TLD instead of the legitimate .com creates a convincing lookalike domain designed to deceive users and AI agents into trusting it as an official Auth0 property. (location: domain: auth0.net)
phishing
auth0.net is a typosquat/lookalike of auth0.com. Auth0 is an identity provider used extensively in authentication flows, making this domain a high-value target for credential harvesting phishing. The TLS connection failed (connected=false, cert_valid=false), meaning the site either serves no valid HTTPS or is misconfigured — consistent with a parked or malicious lookalike domain. (location: domain: auth0.net, TLS status in metadata.json)
credential harvesting
A domain impersonating Auth0 (an identity/SSO provider) is uniquely positioned to harvest OAuth tokens, passwords, and session credentials. Users or automated agents directed to auth0.net instead of auth0.com could submit credentials to an attacker-controlled endpoint. (location: domain: auth0.net)
malicious redirect
The page content is entirely empty (page.html and page-text.txt are blank) while the domain is a known brand lookalike. This is consistent with a parked domain or one that performs silent redirects at the network/DNS level to a phishing destination, or that serves malicious content only under specific conditions (user-agent, geolocation, referrer). (location: page.html (empty), page-text.txt (empty))
prompt injection
An AI agent resolving authentication or identity-related URLs may follow references to auth0.net believing it to be the legitimate Auth0 service. This domain could serve crafted content to manipulate agent behavior, steal tokens passed in headers or query strings, or redirect agent OAuth flows to attacker-controlled endpoints. (location: domain: auth0.net)
curl https://api.brin.sh/domain/auth0.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
auth0.net currently scores 31/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.