context safety score
A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
JavaScript intercepts all clicks and touch events on mobile devices (User-Agent: Mobi|Android) and forcibly redirects to https://susigkeit.com/2100356 for the first 2 interactions per session. Click count is tracked via localStorage to control redirect frequency. The video player controls are withheld until the redirect quota is exhausted, coercing users into triggering redirects. (location: page.html:390-436, script block starting at line 389)
malicious redirect
A second redirect to https://susigkeit.com/2100356 is triggered automatically when any video on the page ends, sending users to the same external destination without consent. (location: page.html:438-447)
social engineering
Dynamically injected Telegram button labeled 'Únete a Telegram' (Join Telegram) linking to https://t.me/+6W_BZOJY6k45Yjlh is inserted adjacent to video elements to lure users into joining an unverified Telegram group. The button is intentionally excluded from the malicious redirect handler, suggesting it is a primary intended destination for user recruitment. (location: page.html:362-385)
hidden content
A third-party widget script is loaded from //waust.at/t.js with identifier '4idqxpsov6' and placed in the page body with no visible label or user-facing description. The waust.at domain is a known traffic analytics/ad network used in gray-area traffic monetization schemes. The widget is injected in the main content area with no visible UI context. (location: page.html:457)
hidden content
The page title tag is empty ('<title> - My WordPress Blog</title>') and the page body contains no visible user-facing text content — only scripts and a blank layout. The site masquerades as a WordPress blog while serving exclusively redirect and Telegram recruitment functionality, concealing its true purpose from casual inspection. (location: page.html:6, page.html:451-461)
social engineering
Aggressive copy-protection and right-click disabling scripts (wpcp_disable_selection, wpcp_disable_Right_Click) prevent users from inspecting or copying page content, reducing the ability of victims or researchers to identify or report the malicious behavior. (location: page.html:108-347)
curl https://api.brin.sh/domain/mekym.usCommon questions teams ask before deciding whether to use this domain in agent workflows.
mekym.us currently scores 38/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.