context safety score
A score of 45/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
Site gold-bets.org (211 days old) operates as a multi-language online gambling/betting affiliate or clone site with login pages across 30+ language locales. The combination of a young domain, mass-generated login pages, and gambling bonus lures is a classic phishing infrastructure pattern used to harvest credentials from users of legitimate betting platforms. (location: https://gold-bets.org/login/ and all locale variants (e.g. /lt/login/, /bn/login/, /bg/login/, etc.) — page.html lines 420-554)
credential harvesting
The sitemap exposes 30+ localized /login/ endpoints (one per language/region), indicating a mass-scale credential collection infrastructure. Legitimate gambling operators do not typically expose dozens of duplicate login pages per locale in their XML sitemap. This pattern is consistent with phishing pages designed to harvest credentials across many user populations. (location: https://gold-bets.org/login/ and all locale variants — page.html lines 420-554)
social engineering
The site structures its entire content around high-conversion gambling lure pages: /bonus/, /no-deposit-bonus/, /promo-code/, and /login/ — each replicated across 30+ language locales. 'No deposit bonus' and 'promo code' pages are well-known social engineering lures used to entice users to register accounts and submit personal/financial information on fraudulent or unlicensed gambling sites. (location: https://gold-bets.org/no-deposit-bonus/, /bonus/, /promo-code/ and all locale variants — page.html lines 8-418)
phishing
The domain gold-bets.org is only 211 days old and has no blocklist entries, consistent with a newly-stood-up phishing or affiliate fraud site that has not yet been reported. The rapid creation of 150+ sitemap URLs across 30 locales within days (timestamps clustered July 31 – August 1, 2025) suggests automated bulk page generation typical of phishing kit deployment. (location: metadata.json — domain_age_days: 211; page.html timestamps lines 5-910)
hidden content
The HTML source contains two repeated debug/error comments at the end of the sitemap XML: '<!-- WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory. -->' repeated twice. While not malicious on its own, these HTML comments leak internal WordPress configuration details (plugin names, config file paths) that could aid targeted attacks against the site's backend. (location: page.html line 912)
curl https://api.brin.sh/domain/gold-bets.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
gold-bets.org 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.