context safety score
A score of 44/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
hidden content
Yandex Metrika tracking pixel loaded via a 0x0 pixel image positioned off-screen at left:-9999px, invisibly tracking all visitors without prominent disclosure. Script injected dynamically via inline JavaScript with obfuscated IIFE pattern. (location: page.html line 268-272, page-text.txt line 268)
hidden content
Third-party script loaded from rap.skcrtxr.com — an unrecognized, suspicious domain with randomized-looking subdomain pattern (skcrtxr). It dynamically injects invisible 0x0 pixel tracking images via window.runRapPixel() using position:absolute, height:0px, width:0px. This is a covert data exfiltration beacon mechanism with no user disclosure. (location: page.html line 5-6)
obfuscated code
Inline script defines window.runRapPixel() which silently appends invisible tracking images to document.body pointing to rap.skcrtxr.com/pub/pix/{token}. The domain skcrtxr.com is not a known analytics provider and the pixel firing pattern is consistent with covert user/session fingerprinting or ad fraud beaconing. (location: page.html line 6)
malicious redirect
External script loaded from cdn.diginetica.net/4631/client.js via script tag with defer/async. Diginetica is a third-party recommendation/search engine SDK; however it is loaded from an external CDN with no subresource integrity (SRI) check, meaning a compromised CDN could inject malicious redirects or credential harvesting code without detection. (location: page.html line 7 (head script tags))
hidden content
The page HTML lang is set to 'ru' and all content is in Russian (Cyrillic), while the scanned domain is polaris-iot.com — a domain name suggesting an IoT/industrial context rather than a Russian consumer appliance retailer. This mismatch between domain name branding and actual site content (polaris.ru consumer electronics) may indicate the domain is being used to proxy or mirror content from the legitimate polaris.ru site. (location: page.html line 2, metadata.json domain field)
curl https://api.brin.sh/domain/polaris-iot.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
polaris-iot.com currently scores 44/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.