context safety score
A score of 41/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 'authenticatorlocalprod.com' impersonates a legitimate authenticator service by embedding the word 'authenticator' in the domain name. The addition of 'localprod' is a common evasion technique to appear as an internal or production environment of a trusted authenticator brand (e.g., Google Authenticator, Microsoft Authenticator), likely intended to deceive users or automated systems into trusting the domain. (location: metadata.json: domain field / URL)
phishing
The domain 'authenticatorlocalprod.com' is highly consistent with phishing infrastructure targeting users of multi-factor authentication (MFA) services. Authenticator-themed domains are frequently used in real-time phishing proxies (AiTM attacks) to intercept OTP codes and session tokens from victims who believe they are accessing a legitimate authenticator portal. (location: metadata.json: url / .brin-context.md)
credential harvesting
The combination of an authenticator-impersonating domain name, failed TLS connection (connected=false, cert_valid=false), and empty page content is consistent with a credential harvesting site that may be dormant, recently stood up, or serving content conditionally (e.g., only to targeted victims via redirected links). Authenticator-themed phishing sites are specifically designed to harvest TOTP codes and passwords. (location: metadata.json: tls fields; page.html and page-text.txt (empty content))
hidden content
The page HTML and visible text are both completely empty despite the domain being live enough to have been scanned. This is anomalous and may indicate the page serves content conditionally based on referrer, user-agent, geolocation, or a specific token in the URL — a common technique to evade automated scanners while still serving malicious content to targeted victims. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty))
malicious redirect
Empty page body combined with an authenticator-impersonating domain suggests the site may function as a redirect intermediary — returning no content to scanners/bots while redirecting targeted victims (arriving via phishing email links) to a credential harvesting page or a real-time AiTM proxy. (location: page.html (empty body); metadata.json: url)
curl https://api.brin.sh/domain/authenticatorlocalprod.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
authenticatorlocalprod.com currently scores 41/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.