context safety score
A score of 43/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
cloaking
Page loads content in transparent or zero-size iframe overlay
obfuscated code
Two instances of obfuscated JavaScript use a custom character-shift decoder (atob + manual charCode rotation with junk dead-code statements) to construct a script URL at runtime and inject it into the DOM with referrerPolicy='unsafe-url'. The decoded payload source is hidden and cannot be statically inspected. First instance in <head> (line 155), second instance duplicated in <body> footer area (line 2234 / page-text.txt line 1974). (location: page.html:155 and page.html:2234)
malicious redirect
The page is served from zmags.com but immediately redirects all canonical references, og:url, and navigation to getfastr.com. The HTML title, meta description, and all content brand as 'Fastr' while the scanned domain is zmags.com. A delayed third-party script (d10lpsik1i8c69.cloudfront.net/w.js) is injected after a 5-second setTimeout, obscuring its load from standard page-load scanners. (location: page.html:146-151 and page.html:127)
hidden content
A 1x1 pixel invisible LinkedIn tracking image (display:none) is embedded twice with different partner IDs (2795618 and 4636244), silently exfiltrating visitor data to LinkedIn's ad network without visible disclosure. Also, a Google Tag Manager noscript iframe (display:none;visibility:hidden) silently loads external tracking in non-JS environments. (location: page.html:2232-2233 and page.html:2250-2251 and page.html:263)
brand impersonation
The scanned URL is zmags.com, but the entire page content, title, metadata, canonical link, and all navigation brand exclusively as 'Fastr' (getfastr.com). Footer states '©2026 All Rights Reserved, Zmags Corp, DBA Fastr'. This domain-brand mismatch could mislead users or automated agents into believing zmags.com is a separate, possibly fraudulent version of the Fastr brand. However, the DBA disclosure in the footer indicates this is likely a legitimate domain redirect rather than malicious impersonation. (location: page.html:7 and page.html:127 and page.html:2098)
curl https://api.brin.sh/domain/zmags.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
zmags.com currently scores 43/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.