context safety score
A score of 35/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
script/meta redirect patterns detected in page source
js obfuscation
JavaScript uses Function constructor for runtime code generation
phishing
The domain simnet.is is hosting a Zimbra Web Client Sign In login page. The domain simnet.is is not affiliated with Zimbra or Synacor. The legitimate Icelandic telecom is siminn.is (note the extra 'n'), while this page at simnet.is impersonates it. The 'Gleymt lykilorð?' (Forgot password?) link points to thjonustuvefur.siminn.is, indicating this page is designed to harvest credentials from siminn.is users who are redirected or tricked into visiting simnet.is instead. (location: https://simnet.is — page.html, entire login form)
credential harvesting
A fully functional username/password login form is hosted on simnet.is with form action='/' submitting credentials via POST. The form includes username and password fields with autocomplete='off' on the password field, a CSRF token (login_csrf), and a 'Stay signed in' checkbox. Credentials entered here would be harvested by whoever controls simnet.is rather than delivered to the legitimate siminn.is email service. (location: page.html lines 44-99 — <form id='zLoginForm' method='post' action='/'>')
brand impersonation
The page fully impersonates the Zimbra Web Client (copyright Synacor, Inc.) and the Icelandic ISP Siminn (siminn.is). All support and terms links point back to legitimate siminn.is domains (thjonustuvefur.siminn.is, adstod.siminn.is, www.siminn.is), reinforcing the deception that this is a genuine siminn.is service portal, while the actual hosting domain is the lookalike simnet.is. (location: page.html lines 24, 72-74, 105 — title, footer links, copyright notice)
malicious redirect
The 'Gleymt lykilorð?' (Forgot password) link points to https://thjonustuvefur.siminn.is/einstaklingar/jsp/internet/lykilord/breyta on the legitimate siminn.is domain. This cross-domain link is used as a trust signal to make victims believe they are on a legitimate siminn.is portal, while credential submission goes to simnet.is. The forgotPassword() JavaScript function also redirects to /public/PasswordRecovery.jsp on the attacker-controlled domain. (location: page.html line 72 and lines 364-374 — forgotPassword() function)
curl https://api.brin.sh/domain/simnet.isCommon questions teams ask before deciding whether to use this domain in agent workflows.
simnet.is currently scores 35/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.