context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
malicious redirect
Two meta refresh tags with content='0;url=...' cause immediate zero-delay redirects. One uses a placeholder 'AAA' and the other redirects to http://www.megaline.co/B30V, a shortened/obfuscated URL on an external domain that bypasses the blogspot.com origin entirely. (location: page.html:635 and page.html:648-651)
malicious redirect
A link and anchor element both point to http://www.megaline.co/B30V, a short-link redirect to an unknown destination. The URL structure (short alphanumeric path B30V) is typical of redirect chains used to obscure final landing pages, commonly used in traffic monetization or malware distribution schemes. (location: page.html:639-646)
social engineering
The page is labeled 'adultcontent' and titled 'adultcontent' with explicit adult link directory content in the sidebar (adult live cams, teen, granny, XXX cam sites). This pattern uses adult content as lure to drive traffic through redirect chains to unknown external destinations. (location: page.html:741-753, page-text.txt:316-325)
hidden content
External third-party JavaScript loaded asynchronously from //x3.xclicks.net/js2/x6678.js under the 'Link Exchange' widget. This is a fully external, unverifiable script from a non-Google domain embedded into the page. xclicks.net is an ad/click-exchange network with no content transparency; the script could inject additional redirects, popups, or tracking without any visible content. (location: page.html:542)
obfuscated code
The post body contains placeholder tokens 'AAA' and 'BBB' used as both image src attributes and href/redirect targets. These appear to be template variables that were never substituted, or intentional obfuscation masking the actual redirect target. Combined with the live megaline.co redirect, this suggests a redirect template that may serve different destinations dynamically or to different user agents. (location: page.html:631-635)
obfuscated code
Tier 2 scan flagged 11 suspicious base64 blobs and JS obfuscation suspected=true. The page contains unicode escape sequences (\x3d, \x22, \u0421, etc.) throughout the _WidgetManager JavaScript block, which is standard Blogger encoding but represents partial obfuscation of string content that could mask injected data. (location: page.html:878-893)
curl https://api.brin.sh/domain/contentadult.blogspot.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
contentadult.blogspot.com 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.