context safety score
A score of 36/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
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
phishing
Page impersonates PayPal login
brand impersonation
The scanned URL is dnainfo.com, but the page serves the full blockclubchicago.org website verbatim, including its canonical URL (https://blockclubchicago.org/), og:url, og:site_name, structured data, and all internal links. dnainfo.com is a defunct local news brand; serving blockclubchicago.org content under this domain constitutes brand impersonation of Block Club Chicago and exploitation of the dnainfo.com legacy domain name. (location: metadata.json:url=https://dnainfo.com vs page.html:17 canonical href=https://blockclubchicago.org/, page.html:22 og:url=https://blockclubchicago.org/)
malicious redirect
Traffic arriving at dnainfo.com is silently served the complete blockclubchicago.org homepage without any redirect notice to the user. All resource URLs, authentication endpoints, payment flows (WooCommerce/PayPal), and subscription forms resolve to blockclubchicago.org, meaning users interacting with the page under the dnainfo.com domain are unknowingly transacting with a different site's infrastructure. (location: metadata.json:url=https://dnainfo.com vs page.html body content referencing blockclubchicago.org throughout)
hidden content
Infolinks ad-injection script is loaded (resources.infolinks.com/js/infolinks_main.js) with publisher ID 3418886. Infolinks dynamically rewrites page text by converting keywords into third-party affiliate/ad hyperlinks invisible to the site owner, injecting undisclosed commercial content into editorial news copy. jQuery manipulation wraps h1 tags and .description elements with INFOLINKS_OFF/ON comment sentinels to control injection zones. (location: page.html:2135-2142 (Infolinks START block), page-hidden.txt:177-186)
social engineering
The page presents a fully functional Block Club Chicago sign-in and newsletter subscription modal under the dnainfo.com domain. Users who enter their email address or credentials into these forms may not realize they are submitting data while browsing what appears to be a different brand (dnainfo.com), creating a deceptive trust context. (location: page.html:sign-in modal and newsletter signup modal; page-text.txt:1532-1633)
curl https://api.brin.sh/domain/dnainfo.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
dnainfo.com currently scores 36/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.