context safety score
A score of 32/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
hidden content
Both page.html and page-text.txt are PNG binary image files served with misleading extensions. Delivering page content as images rather than readable HTML/text evades text-based content scanners and hides the true nature of the page from automated analysis tools and AI agents. (location: page.html, page-text.txt)
obfuscated code
Page content is encoded as PNG image data instead of HTML/text, a deliberate obfuscation technique to prevent automated threat analysis, content inspection, and prompt injection detection by AI agents. (location: page.html (265092 bytes PNG), page-text.txt (216574 bytes PNG))
phishing
Domain 'servicio-online.net' uses a generic Spanish-language phrase ('online service') commonly used to impersonate Spanish-language banking, government, or utility portals. Combined with invalid TLS and image-based content obfuscation, the site exhibits multiple hallmarks of an active phishing operation. (location: metadata.json: domain=servicio-online.net)
brand impersonation
The domain name 'servicio-online.net' closely mimics branding patterns used by Spanish-language financial institutions and government services (e.g., Banco Santander, BBVA, Hacienda, Seguridad Social). The generic 'servicio online' phrasing is a known tactic to impersonate official service portals. (location: metadata.json: url=https://servicio-online.net)
credential harvesting
Combination of phishing domain, obfuscated image-based page content (preventing scanner inspection), and invalid TLS is consistent with a credential harvesting page that conceals its login form content from automated detection. (location: page.html, metadata.json)
malicious redirect
TLS connection failed (connected=false, cert_valid=false) despite the URL using HTTPS scheme. This inconsistency may indicate the site redirects users or operates infrastructure designed to intercept or manipulate traffic outside of standard TLS validation. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
curl https://api.brin.sh/domain/servicio-online.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
servicio-online.net currently scores 32/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.