context safety score
A score of 58/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The domain forteba-mikronauta.hydr0.org serves content cloned from mp3.cc (canonical tag, all links, branding, and assets point to mp3.cc), while the actual serving domain is a subdomain of hydr0.org. The page includes a redirect (1 detected in Tier 2) that routes visitors away from the expected domain to the real mp3.cc infrastructure, creating a deceptive intermediary domain. (location: metadata.json: url=https://forteba-mikronauta.hydr0.org; page.html line 9: canonical href points to mp3.cc)
brand impersonation
The page fully impersonates MP3.cc — including its logo, title tag ('Forteba Mikronauta | Download mp3 free, listen music online - MP3.cc'), og:site_name, og:image, all navigation links, footer copyright, and stylesheet/JS assets — while being hosted on a third-party subdomain (forteba-mikronauta.hydr0.org) unaffiliated with mp3.cc. (location: page.html lines 5, 11, 18-19, 33-36, 304-310)
malicious redirect
Audio streaming URLs use fine.sunproxy.net as a proxy/intermediary rather than direct mp3.cc infrastructure. The base64-encoded path parameters in these URLs (4 suspicious base64 blobs flagged in Tier 2) obfuscate the actual file routing through a third-party proxy server, which could intercept traffic or serve malicious payloads. (location: page.html lines 228, 247, 266, 285: data-url attributes pointing to fine.sunproxy.net/file/<base64>)
hidden content
The HTML comment on line 391 contains a server-side timing/fingerprinting string: '<!-- 0.6132; 1 (0.00056982040405273). (US|). -->' which leaks server performance metrics and geo-targeting data (US region identifier), potentially used for user profiling or bot/agent detection to serve different content to crawlers. (location: page.html line 391: HTML comment with timing and geo metadata)
curl https://api.brin.sh/domain/forteba-mikronauta.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
forteba-mikronauta.hydr0.org currently scores 58/100 with a caution verdict and medium 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.