context safety score
A score of 45/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
brand impersonation
The page is served from domain bucoup.com but the HTML title tag reads 'AdSurge' and all static assets, fonts, and OneTrust consent scripts are loaded from sdkstatic.adsurge.com and cdn-ukwest.onetrust.com configured for www.adsurge.com (OneTrust domain-script ID tied to adsurge.com). The domain bucoup.com has no apparent relationship to the AdSurge brand, indicating the site is impersonating or spoofing the AdSurge platform. (location: page.html:<title> (line 7), OneTrust script data-domain-script for adsurge.com (lines 11-16), font preload from sdkstatic.adsurge.com (line 8))
malicious redirect
The domain bucoup.com (233 days old) fully renders its UI via a heavily split JavaScript bundle (26 vendor JS chunks plus an index bundle) loaded client-side into a single empty <div id='root'>. All real content and navigation logic are deferred to these opaque bundles, making it impossible to inspect destination URLs, redirect targets, or ad payloads statically. This pattern is commonly used to hide post-load redirects or malvertising payloads from static scanners. (location: page.html:31 — 26 deferred vendor JS bundles + /assets/js/index.980b7c16.js)
hidden content
The visible page text (page-text.txt) is entirely empty — only whitespace. All content is injected dynamically by JavaScript bundles after page load. This means any phishing forms, credential-harvesting UI, or social-engineering copy would be invisible to static crawlers and text-based analysis. (location: page-text.txt (lines 1-4); page.html:34 — <div id='root' class='odc-offical-app'>)
brand impersonation
The CSS class 'odc-offical-app' on the root div contains a misspelling ('offical' instead of 'official'). This is a common indicator of a hastily constructed clone or impersonation site rather than a legitimate branded application. (location: page.html:34 — <div id='root' class='odc-offical-app'>)
curl https://api.brin.sh/domain/bucoup.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
bucoup.com currently scores 45/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.