context safety score
A score of 70/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
hidden content
Multiple machine-readable timestamps are rendered with display:none (e.g., <span class="updated" style="display:none;">2020-03-19T04:42:30+00:00</span>), inflating the hidden-content ratio. These are standard WordPress/schema.org microformat fields and are not malicious, but contribute to the flagged hidden content ratio of 0.02. (location: page.html:3460, 3576, 3617, 3658 (and throughout post meta spans))
social engineering
A blog post for 'ArchAngel Video – Ultimate Brunettes 2' contains injected promotional paragraph advertising external adult content with the anchor text 'free naked girls galleries' linking to hotnakedwomen.com. This paragraph is stylistically inconsistent with surrounding press-release content and appears to be a third-party link injection inserted to drive traffic to an unrelated off-domain adult aggregator site. (location: page.html:3565)
malicious redirect
The site's navigation sidebar contains four off-domain affiliate/link-farm entries pointing to nudeof.com, bigbootytube.net, hornybank.com, and hairywomen.tv. These are rendered as visible menu items in a secondary navigation widget, consistent with paid link placement or a compromised widget area directing users away from the legitimate site. (location: page.html:3414-3417)
hidden content
Tier 2 scanner flagged 12 suspicious base64 blobs. Review of page.html shows these correspond to standard WordPress emoji detection logic (canvas toDataURL calls using String.fromCharCode with Unicode surrogate pairs) and are not encoding any injected payload or exfiltration strings. This is a false positive. (location: page.html:62-83 (wp-emoji inline script))
curl https://api.brin.sh/domain/archangelblog.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
archangelblog.com currently scores 70/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.