context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
domain spoof risk
domain has spoofing indicators (punycode/confusable/highly synthetic naming)
tls connection failed
Could not establish TLS connection
brand impersonation
The domain xn--b1aew.xn--p1ai is an IDN (Internationalized Domain Name) encoded in Punycode. Decoded, xn--b1aew resolves to the Cyrillic string мвд (MVD), which is the abbreviation for Министерство внутренних дел (Russian Ministry of Internal Affairs/Police). The TLD xn--p1ai is the Punycode for .rf (рф), the official Russian ccTLD. This domain impersonates the official Russian federal law enforcement agency (MVD/МВД), a high-value government brand commonly targeted for phishing and social engineering campaigns targeting Russian citizens. (location: domain: xn--b1aew.xn--p1ai)
phishing
The domain mimics the official Russian Ministry of Internal Affairs (MVD МВД) using homograph/IDN techniques. Government impersonation domains of this type are a well-established phishing vector used to deceive citizens into submitting personal data, credentials, or payments under the false belief they are interacting with a legitimate government authority. The TLS connection failed (connected=false, cert_valid=false), meaning the site does not present a valid certificate, consistent with a fraudulent or poorly-maintained impersonation site. (location: domain: xn--b1aew.xn--p1ai; TLS status: connected=false, cert_valid=false)
hidden content
TLS connection to the site failed entirely (connected=false), which prevented retrieval of page content. The page.html, page-text.txt, and page-hidden.txt files are all empty. The actual page content and any embedded threats (scripts, hidden fields, redirects, injected prompts) could not be analyzed. The absence of content due to TLS failure means threats may be present but undetected. (location: page.html, page-text.txt, page-hidden.txt (all empty due to TLS connection failure))
curl https://api.brin.sh/domain/xn--b1aew.xn--p1aiCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--b1aew.xn--p1ai currently scores 49/100 with a suspicious verdict and medium 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.