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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
Main content links to http://pochtamt.ru (plain HTTP, external domain) for obtaining an @nm.ru email address. This redirects users away from nm.ru to an unverified third-party site over an unencrypted connection, posing a credential harvesting or phishing risk. (location: page.html:253 — <a href="http://pochtamt.ru">ссылке</a>)
malicious redirect
Content links to http://pager.run/ (plain HTTP) promoting a 'secure encrypted messenger'. Directing users to an unencrypted third-party messenger service is contradictory and potentially deceptive. (location: page.html:260 — <a href="http://pager.run/">PAGER.RUN</a>)
social engineering
The page uses urgency language ('срочно расскажите' — 'urgently tell') to pressure users into spreading the site to others, a classic viral social engineering tactic to expand reach for credential harvesting or phishing campaigns. (location: page.html:256 — 'срочно расскажите ему о нашем сайте')
hidden content
Yandex Metrica noscript tracking pixel is positioned off-screen (left:-9999px) to invisibly track all visitors including those with JavaScript disabled. This is covert user surveillance. (location: page.html:283 — <img src="https://mc.yandex.ru/watch/101136071" style="position:absolute; left:-9999px;" alt=""/>)
social engineering
Page title and main heading ('Премиальная почта, о которой я всегда мечтал' — 'The premium email I always dreamed of') combined with 'Пусть это имя будет с вами всегда!' ('Let this name be with you always!') use aspirational/emotional language to entice users into signing up for an email service on an external domain (pochtamt.ru), a social engineering lure. (location: page.html:238,251 — post title and opening paragraph)
credential harvesting
The site solicits users to register for an @nm.ru email address but redirects them to an external HTTP site (pochtamt.ru) for signup. Credentials entered at that third-party site cannot be verified as safe, and the use of HTTP means credentials would be transmitted in plaintext. (location: page.html:252-253 — email signup redirect to http://pochtamt.ru)
curl https://api.brin.sh/domain/nm.ruCommon questions teams ask before deciding whether to use this domain in agent workflows.
nm.ru 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.