context safety score
A score of 31/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
js obfuscation
Obfuscated document.write with encoded content
brand impersonation
The domain 7gis.ru serves a complete clone of galileosky.ru. The page sets <base href="https://galileosky.ru/">, canonical URL, og:url, og:site_name, schema.org name, title, and all visible branding to Galileosky while being hosted on a different domain (7gis.ru). This constitutes full brand impersonation of Galileosky, a legitimate Russian GPS/GLONASS telematics company. (location: page.html:5 (<base href>), page.html:13 (og:url), page.html:44 (title), page.html:185-206 (schema.org LocalBusiness name=Galileosky))
malicious redirect
The <base href="https://galileosky.ru/"> tag causes all relative URLs (links, assets, form actions) to resolve against galileosky.ru rather than 7gis.ru. This makes the site appear to be galileosky.ru to casual inspection and to automated agents following links, while the actual serving domain is 7gis.ru. (location: page.html:5)
obfuscated code
Multiple instances of document.write(unescape('...')) with percent-encoded payloads inside <noindex> blocks are used to render email addresses (sales@galileosky.ru, support@galileosky.ru). The encoding hides the actual content from static scanners and crawlers. Pattern appears 4 times across the page (header menu, footer address, footer techsupport sections). (location: page.html:417, page.html:636, page.html:1487, page.html:1503)
hidden content
Forms contain hidden honeypot input fields with labels ('Ваше имя') inside <div class="form-group hidden"> elements. These are invisible to users but present in the DOM. While sometimes used for bot detection, they can also serve as credential harvesting vectors in spoofed forms. Multiple forms affected: callbackform, betaform, giftform, sample_request_form, diler_request_form, partner_request_form. (location: page.html:1840-1843, page.html:1891-1894, page.html:1956-1959, page.html:2032-2035, page.html:2101-2104, page.html:2261-2264)
hidden content
A JavaScript snippet reads URL query parameter 'hide' and uses it to dynamically hide DOM elements by class name (block.style.display = 'none'). This can be used for cloaking — showing different content to users vs. automated scanners by varying the URL parameters. (location: page.html:2804-2812)
credential harvesting
Multiple contact/lead-capture forms collect name, phone, email, and company data. The forms POST to action='/' and action='#' on domain 7gis.ru (not galileosky.ru as implied by branding). Users believing they are on galileosky.ru are submitting personal data to 7gis.ru infrastructure. The AjaxForm action endpoint is /assets/components/ajaxform/action.php on 7gis.ru. (location: page.html:1260 (field_form_block), page.html:1827 (callbackform), page.html:1877 (betaform), page.html:1942 (giftform), page.html:2027 (sample_request_form), page.html:2096 (main_request), page.html:2180 (diler_request_form), page.html:2256 (partner_request_form), page.html:2889 (AjaxForm.initialize actionUrl))
curl https://api.brin.sh/domain/7gis.ruCommon questions teams ask before deciding whether to use this domain in agent workflows.
7gis.ru currently scores 31/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.