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
phishing
Domain 'linkpenidabet.com' follows a pattern commonly used in gambling/betting phishing lures ('penidabet' suggests a betting brand), with no TLS connection established (TLS connected=false, cert_valid=false), meaning credentials or user data would be transmitted insecurely. The combination of a relatively young domain (321 days), unknown hosting reputation, and failed TLS is consistent with a phishing or credential-harvesting site. (location: metadata.json: domain=linkpenidabet.com, tls.connected=false, tls.cert_valid=false)
credential harvesting
The site fails TLS validation entirely (connected=false, cert_valid=false, san_match=false), meaning any form submissions — login credentials, payment data, or personal information — would be sent without encryption. This is a hallmark of credential harvesting infrastructure designed to capture user input in plaintext. (location: metadata.json: tls object — connected=false, cert_valid=false, san_match=false)
brand impersonation
The domain 'linkpenidabet.com' contains 'penidabet', which appears to impersonate or spoof a betting/gambling brand (possibly 'Penida Bet' or a similar regional brand). Use of 'link' as a subdomain-style prefix in the apex domain is a common technique to impersonate a legitimate brand's link-shortener or referral portal. (location: metadata.json: domain=linkpenidabet.com)
social engineering
The domain name structure ('link' + brand-name + 'bet') is a recognized social engineering pattern used to create fake referral or bonus-claim pages that trick users into submitting credentials or making deposits to fraudulent gambling platforms. The 321-day-old domain with unknown hosting reputation supports this pattern. (location: metadata.json: domain=linkpenidabet.com, whois.domain_age_days=321, hosting.reputation=Unknown)
curl https://api.brin.sh/domain/linkpenidabet.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
linkpenidabet.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.