context safety score
A score of 56/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
brand impersonation
The site is titled 'Downtown Titusville' and uses the domain downtowntitusville.org, but the entire page content, metadata, and UI are in German (lang='de', og:locale='de_DE', German navigation labels, German body text). Titusville is a city in Florida, USA. A legitimate downtown association for a US city would not operate entirely in German. This is a strong indicator that the site impersonates a real US local organization while targeting a German-speaking audience, likely for fraudulent real-estate investment solicitation. (location: page.html:2-3, metadata og:locale, page.html:14,21,27)
social engineering
The site was registered only 36 days ago (domain_age_days: 36) and presents itself as a 'leading real estate blog' (Führender Immobilienblog) for downtown Titusville, FL, while operating entirely in German. It repeatedly urges visitors to 'contact us' for 'investment opportunities' and 'tailored investment advice' (maßgeschneiderte Beratung). This pattern — new domain, mismatched language/geography, urgent investment CTAs — is consistent with a fraudulent investment solicitation scheme. (location: page.html:229,245,285,315; metadata.json whois.domain_age_days=36)
social engineering
Multiple high-pressure calls-to-action ('Jetzt entdecken', 'Starten Sie Ihre Investitionsreise noch heute', 'Kontaktieren Sie uns jetzt') are used throughout the page to push visitors toward a contact form, consistent with investment fraud or lead-generation scam tactics. (location: page.html:229,285,315)
hidden content
The pre-scan detected a hidden content ratio of 0.08 and 6 suspicious base64 blobs. While no confirmed injection or exfiltration hits were found, the base64 blobs warrant further inspection. The page also contains an empty container block (uagb-block-308485a9) with no visible content, which could be a placeholder for dynamically injected content. (location: .brin-context.md: hidden_content_ratio=0.08, suspicious_base64_blobs=6; page.html:320)
curl https://api.brin.sh/domain/downtowntitusville.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
downtowntitusville.org currently scores 56/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.