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
encoded payload
suspicious base64-like blobs detected in page content
brand impersonation
The site enti33.it presents itself as 'Pubblica Amministrazione' (Italian Public Administration) using official Italian government design system (bootstrap-italia), government logos (it-pa SVG sprite), and official-looking branding, but is operated by a private entity 'PA33 s.r.l.' as revealed by the visually-hidden anchor tag. The domain 'enti33.it' is not an official Italian government domain (which use .gov.it). This constitutes impersonation of Italian public administration to deceive users. (location: page.html:20-31, page.html:98)
hidden content
A visually-hidden anchor element (<a class='visually-hidden' href='https://pa33.it/' aria-label='PA33 s.r.l.'>) is present in the page. This element is hidden from normal users using CSS but reveals the true operator (PA33 s.r.l.) and links to a separate domain (pa33.it). This pattern is used to conceal the real commercial entity behind a facade of public administration branding. (location: page.html:98)
social engineering
The site impersonates Italian Public Administration ('Pubblica Amministrazione') with official government styling, logos, and design patterns to establish false trust. The main content area is empty (<h1 class='pb-2'></h1>) and the Blazor app fails to load, suggesting the site may be in a pre-deployment phishing staging state or is designed to serve malicious content dynamically via Blazor server-side rendering after initial page load. (location: page.html:44, page.html:20-43)
malicious redirect
TLS is not connected and certificate is invalid (connected=false, cert_valid=false) for https://enti33.it. The site is being served over a domain claiming HTTPS but without a valid TLS certificate, which could indicate a man-in-the-middle setup or that the site is intercepting traffic. Social media links (Facebook, Twitter) both point to '/' instead of real social profiles, a pattern common in cloned/impersonation sites. (location: metadata.json:1, page.html:35-36)
curl https://api.brin.sh/domain/enti33.itCommon questions teams ask before deciding whether to use this domain in agent workflows.
enti33.it 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.