context safety score
A score of 47/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
cloaking
Page loads content in transparent or zero-size iframe overlay
malicious redirect
The email subscription form in the footer submits to 'https://urtr.us7.list-manage.com/subscribe/post' — the domain 'urtr.us7.list-manage.com' uses a subdomain pattern that looks like Mailchimp's list-manage.com, but the subdomain prefix is 'urtr' which is a typosquat of 'ustr' (the official agency acronym). Legitimate USTR Mailchimp forms would use a subdomain matching the organization. This could redirect user-submitted email addresses to an attacker-controlled list endpoint. (location: page.html:454 — form action URL: https://urtr.us7.list-manage.com/subscribe/post?u=b58f12c4da47019d98a1e84ef&id=df7e2dfbfe)
credential harvesting
The email subscription form collects user email addresses and submits them to an external domain 'urtr.us7.list-manage.com' — a likely typosquat of 'ustr' — rather than a verified USTR-controlled endpoint. Users trusting the official ustr.gov site may submit their email to an attacker-controlled mailing list collector. (location: page.html:454-470 — #mc-embedded-subscribe-form targeting urtr.us7.list-manage.com)
hidden content
A hidden honeypot input field is present in the subscription form with inline style 'position: absolute; left: -5000px; display:none;' and aria-hidden='true'. While this is a standard Mailchimp anti-bot technique, its presence on a form pointing to a suspicious domain (urtr vs ustr) warrants flagging as it is not visible to users. (location: page.html:467 — <div style='position: absolute; left: -5000px;display:none;' aria-hidden='true'>)
hidden content
Inline CSS is injected directly inside a hero anchor tag body ('.priorities-section { background-position: center; }') rather than in a stylesheet, which is unusual and could be a vector for style injection or content manipulation in contexts where HTML is parsed by agents. (location: page.html:246-250 — <style> block inside hero <a> tag)
brand impersonation
The page correctly presents as ustr.gov (United States Trade Representative) with consistent branding, leadership bios, and official content. No external brand impersonation of third parties is detected. Domain age of 15037 days (~41 years), valid TLS, and no blocklist hits support legitimacy. Note: the suspicious Mailchimp subdomain 'urtr' may impersonate USTR's own brand in the context of that form endpoint. (location: metadata.json — domain: ustr.gov, page.html overall structure)
curl https://api.brin.sh/domain/ustr.govCommon questions teams ask before deciding whether to use this domain in agent workflows.
ustr.gov currently scores 47/100 with a suspicious 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.