context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
social engineering
Domain '66lottery20.com' uses a numbered lottery brand pattern (incremented number suffix '20') consistent with a rotating network of gambling/lottery scam sites that cycle through enumerated domains to evade blocklists. This is a recognized social engineering tactic to lure users with lottery or prize win promises. (location: domain: 66lottery20.com)
phishing
TLS is not connected and certificate is invalid (connected=false, cert_valid=false, san_match=false). A site soliciting user interaction or credentials over an insecure, unverified connection presents a significant phishing risk, as sensitive data could be intercepted or the site may be a fraudulent impersonation. (location: metadata.json: tls object)
brand impersonation
The domain '66lottery20.com' mimics the naming convention of the widely-known '66lottery' gambling brand. The appended numeral '20' is a classic domain squatting / brand impersonation pattern used to ride on the trust of an established brand name while operating as a separate, potentially fraudulent entity. (location: domain: 66lottery20.com)
malicious redirect
The page HTML and page text are completely empty despite the site being reachable enough to have metadata collected. This is consistent with a redirect-only or cloaking setup where the real malicious content is delivered via JavaScript redirect or server-side redirect after initial load, hiding the true destination from static scanners. (location: page.html, page-text.txt (both empty))
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are empty, yet the domain resolves and metadata was collected. This absence of visible or hidden content suggests aggressive cloaking, bot-detection-based content suppression, or dynamic content delivery designed to evade automated security scanning. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/66lottery20.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
66lottery20.com currently scores 40/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.