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
brand impersonation
The domain aces-eights-1st-tna-theme.hydr0.org fully impersonates mp3.cc: the page title, canonical URL, og:site_name, og:url, logo, CSS, JS, and footer copyright all reference mp3.cc while the serving domain is hydr0.org. This is a typosquatting/mirror site masquerading as the legitimate mp3.cc service. (location: page.html:<head> canonical, og tags, footer#foo-copyright; metadata.json:domain)
malicious redirect
The page sets a canonical URL pointing to https://mp3.cc/t/1082948468-aces-eights-1st-tna-theme/ and the serving domain hydr0.org redirects visitors to mp3.cc. This redirect, combined with brand impersonation, is consistent with a traffic-hijacking proxy site that intercepts requests to a cloned music service. (location: page.html:line 9 (rel=canonical); .brin-context.md: Redirects: 1)
malicious redirect
All 20 audio play links use base64-encoded proxy URLs routing through fine.sunproxy.net rather than mp3.cc directly. The base64 blobs encode file paths through an undisclosed third-party proxy, obscuring the true download endpoint and enabling potential traffic interception or malware delivery via audio files. (location: page.html:lines 228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 (data-url attributes); .brin-context.md: Suspicious base64 blobs: 12)
social engineering
A sidebar link labeled 'Online Radio' with a radio/antenna icon links to https://looz.net/ (an unrelated external domain), styled identically to genre navigation links (Pop, Dance, Rap, etc.). This deceptive presentation disguises an off-brand outbound link as legitimate site navigation, consistent with the deceptive_link_count: 1 flag. (location: page.html:lines 204-215 (looz.net anchor in genres-list); .brin-context.md: Deceptive link count: 1)
curl https://api.brin.sh/domain/aces-eights-1st-tna-theme.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
aces-eights-1st-tna-theme.hydr0.org 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.