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
brand impersonation
Domain 'bitkeep.fun' closely mimics 'BitKeep', a legitimate cryptocurrency wallet brand. The use of the exact brand name with a non-standard TLD (.fun instead of .com/.io) is a classic brand impersonation pattern used in crypto phishing campaigns to deceive users into visiting a fraudulent site. (location: domain: bitkeep.fun)
phishing
The combination of a brand-impersonating domain name, invalid/absent TLS certificate, and no accessible page content is consistent with a phishing infrastructure site. Crypto wallet phishing sites using BitKeep's brand have been documented in the wild. The site may serve malicious content selectively (e.g., only to targeted traffic or mobile users). (location: domain: bitkeep.fun, TLS status: connected=false, cert_valid=false)
credential harvesting
BitKeep impersonation sites are commonly used to harvest seed phrases and private keys by presenting fake wallet import or recovery flows. The domain pattern matches known credential-harvesting campaigns targeting BitKeep wallet users. (location: domain: bitkeep.fun)
malicious redirect
The site returned no content during scanning, which may indicate selective content delivery — serving benign or empty responses to scanners/bots while redirecting real users to a phishing payload or a malicious wallet download page. (location: page.html: empty, page-text.txt: empty)
hidden content
All page content files (page.html, page-text.txt, page-hidden.txt) are completely empty despite the domain resolving. This suggests the site may employ cloaking techniques, serving content only under specific user-agent, referrer, or geolocation conditions to evade automated scanning. (location: page.html: 0 bytes, page-text.txt: 0 bytes, page-hidden.txt: 0 bytes)
curl https://api.brin.sh/domain/bitkeep.funCommon questions teams ask before deciding whether to use this domain in agent workflows.
bitkeep.fun 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.