context safety score
A score of 48/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page uses meta refresh redirect
brand impersonation
The page loads RainLoop webmail (v1.14.0) on the domain excellmedia.net with a favicon served from mail.excellmedia.net. RainLoop is a self-hosted webmail client. Hosting a publicly accessible webmail login interface on a domain with no visible branding or page text is a common pattern for credential-harvesting phishing pages that impersonate legitimate email providers. (location: page.html: <link rel='shortcut icon' href='https://mail.excellmedia.net/favicon.ico'/>, rainloop/v/1.14.0/)
credential harvesting
The page is a RainLoop webmail login interface (v1.14.0) with robots meta tag set to 'noindex,nofollow,noodp', actively suppressing search engine indexing. The page-text.txt is entirely empty, meaning no visible content is rendered server-side — the login form is fully JavaScript-rendered, making automated detection harder. This combination (hidden from search engines, JS-only rendering, webmail login) is consistent with a credential harvesting setup targeting email account credentials. (location: page.html: <meta name='robots' content='noindex,nofollow,noodp'/>, page-text.txt (empty))
malicious redirect
A noscript meta-refresh redirect is present, silently redirecting users without JavaScript to './?/NoScript'. An IE8 conditional comment also triggers a meta-refresh redirect to './?/BadBrowser'. While these may be functional redirects for the webmail app, they can be used to redirect non-JS or legacy-browser victims to alternate phishing payloads. (location: page.html line 1: <noscript><meta http-equiv='refresh' content='0; URL=./?/NoScript'/></noscript> and <!--[if lte IE 8]><meta http-equiv='refresh' content='0; URL=./?/BadBrowser'/>)
hidden content
The page-text.txt is completely empty despite the page loading a full webmail application. All content is hidden behind JavaScript rendering, meaning static scanners and screen readers see nothing. This deliberate obscuring of page content is a hiding technique that can evade content-based phishing filters. (location: page-text.txt (0 bytes), page.html: <div id='rl-app'></div> (empty shell, JS-rendered))
curl https://api.brin.sh/domain/excellmedia.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
excellmedia.net 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.