context safety score
A score of 69/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
5 deceptive links where visible host does not match destination host
malicious redirect
A hotel booking button uses a malformed URL 'https://www.hotel.dehttps://www.hotel.de/Booking.aspx?...' where the domain and protocol are concatenated incorrectly, producing the invalid hostname 'www.hotel.dehttps'. This broken URL could redirect users to an unintended or attacker-controlled destination if the browser resolves the malformed scheme, and appears to be a deceptive link counted among the 5 flagged by the scanner. (location: page.html:219 - window.open('https://www.hotel.dehttps://www.hotel.de/Booking.aspx?h_validate=1&h_hmid=116566...'))
malicious redirect
A hidden overlay div (id='Layer2') contains an image map with a large clickable area that silently redirects users to 'https://partners.webmasterplan.com/click.asp?ref=249120&site=2941&type=b95&bnb=95' via an undisclosed affiliate redirect. The layer is rendered as a GIF image popup with no visible URL disclosure to the user, using JavaScript onclick rather than a transparent anchor href, obscuring the true destination. (location: page.html:321-325 - <div id='Layer2' class='layer'> / <area shape='poly' ... onClick="layer_upper('https://partners.webmasterplan.com/click.asp?...')">)
malicious redirect
Four autoscout24 affiliate click URLs embed a diurl parameter containing a mixed-protocol redirect: the outer URL is HTTPS but the diurl value begins with 'http://' (unencrypted), and the diurl itself encodes a nested 'site=' parameter pointing to a second URL. This multi-hop open redirect chain (click.autoscout24.de -> affilinet -> autoscout24.de listing) with an unresolved '$ref$' placeholder in utm_campaign may indicate incomplete or manipulated affiliate tracking links. (location: page.html:270,275,280,285 - window.open('https://click.autoscout24.de/click.asp?ref=249120&site=1679&type=text&tnb=36&diurl= http%3A%2F%2Fwww.autoscout24.de...'))
curl https://api.brin.sh/domain/dortmund.staedte-info.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
dortmund.staedte-info.net currently scores 69/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.