context safety score
A score of 40/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
cloaking
Page loads content in transparent or zero-size iframe overlay
brand impersonation
The URL being scanned is marketwire.com, but the page fully presents itself as GlobeNewswire (globenewswire.com), including the page title 'Press Release & News Distribution | GlobeNewswire', canonical link pointing to www.globenewswire.com, all branding, logos, and application settings referencing globenewswire.com. marketwire.com is serving content that impersonates the GlobeNewswire brand without being the legitimate GlobeNewswire domain. (location: page.html:41, page.html:64, page.html:100-103)
malicious redirect
The canonical URL and all internal hrefs point to www.globenewswire.com rather than the scanned domain marketwire.com. The page silently redirects user identity and session context to globenewswire.com and pnrlogin.globenewswire.com for authentication flows, meaning users who land on marketwire.com are funneled through a different domain's login and registration infrastructure. (location: page.html:64-68, page.html:115-118)
credential harvesting
Sign-in and registration links direct users to pnrlogin.globenewswire.com and portal.notified.com — third-party authentication domains — rather than the scanned domain marketwire.com. A user arriving at marketwire.com and clicking 'Sign in' is sent to pnrlogin.globenewswire.com/en/reset/confirmresetpassword and pnrlogin.globenewswire.com/en/register. This cross-domain credential flow from a domain impersonating another brand is a credential harvesting pattern. (location: page.html:115-118, page.html:270-282)
hidden content
Two zero-dimension GTM noscript iframes (height=0, width=0, display:none, visibility:hidden) are embedded in the page body. While GTM iframes are common, their presence on a domain serving impersonated brand content elevates the risk that tracking or data exfiltration is occurring without user awareness. (location: page.html:82-83)
social engineering
The page uses urgency and authority cues such as '#1 in Press Release Distribution on G2', 'Trusted by Fortune 100 companies', and calls-to-action like 'Take Control of Your Story' and 'Get Started Now' to build false trust and drive user registration/sign-in on a domain (marketwire.com) that is not the legitimate owner of the GlobeNewswire brand being displayed. (location: page.html:549, page.html:505, page.html:386, page.html:476)
curl https://api.brin.sh/domain/marketwire.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
marketwire.com currently scores 40/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.