context safety score
A score of 48/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
TLS connection failed (connected=false, cert_valid=false, san_match=false) for a site claiming to be a government tax authority. This indicates the site cannot be verified as the legitimate agenciatributaria.gob.es and may be an impostor or misconfigured site intercepting traffic. (location: metadata.json: tls fields)
brand impersonation
The domain agenciatributaria.gob.es presents itself as the Spanish Tax Agency (Agencia Tributaria), a high-value government brand commonly targeted by phishing campaigns. The TLS failure means the site's identity cannot be cryptographically verified, raising significant impersonation risk. (location: metadata.json: domain=agenciatributaria.gob.es, tls.connected=false)
phishing
Combination of factors indicates elevated phishing risk: TLS handshake failure (site unreachable or certificate mismatch), government tax authority branding (a primary phishing target), and empty page content suggesting the site may be under construction as a credential-harvesting lure or that content was blocked/stripped during crawl. Real tax authority portals maintain valid TLS. (location: metadata.json, page.html (empty), page-text.txt (empty))
curl https://api.brin.sh/domain/agenciatributaria.gob.esCommon questions teams ask before deciding whether to use this domain in agent workflows.
agenciatributaria.gob.es currently scores 48/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.