context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
Domain 'search-start.org' uses a hyphenated construction mimicking legitimate search engine or browser start page services (e.g., Google, Bing start pages). This pattern is commonly used in phishing sites targeting users seeking search or browser homepage products. (location: metadata.json: domain=search-start.org)
brand impersonation
The domain name 'search-start.org' appears designed to impersonate or ride the brand recognition of well-known search engines or browser start page features. Use of 'search' and 'start' combined with a non-commercial TLD (.org) is a classic brand-adjacent squatting pattern. (location: metadata.json: domain=search-start.org)
malicious redirect
The site failed TLS connection (connected=false, cert_valid=false, san_match=false) yet the URL is HTTPS. This misconfiguration is consistent with a site that may redirect users to another destination after an initial connection attempt, or is serving content via an intermediary. The page HTML and text content are both completely empty, suggesting the real payload is delivered via redirect or client-side script not captured at crawl time. (location: metadata.json: tls.connected=false, tls.cert_valid=false; page.html and page-text.txt are empty)
hidden content
The page HTML, visible text, and hidden text extractions are all empty files, yet the domain resolves and was scanned. This absence of content is anomalous and may indicate content is only rendered in specific browser environments, after JavaScript execution, or conditionally served to evade automated scanners — a common evasion technique used by malicious sites. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty))
social engineering
Domain is only 194 days old with no WHOIS privacy redaction and unknown hosting reputation. Young domains with search/start themed names are frequently registered for short-term social engineering campaigns targeting users looking for browser homepage or search engine tools. (location: metadata.json: whois.domain_age_days=194, hosting.reputation=Unknown)
curl https://api.brin.sh/domain/search-start.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
search-start.org currently scores 42/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.