context safety score
A score of 46/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 'gymsharkapps.io' impersonates the well-known athletic apparel brand Gymshark (gymshark.com) by appending 'apps' to the brand name under a different TLD (.io). This pattern is commonly used in typosquatting and brand impersonation campaigns to deceive users into believing they are interacting with an official Gymshark property. (location: domain: gymsharkapps.io)
phishing
The site uses a Gymshark brand-lookalike domain (gymsharkapps.io) with a failed/invalid TLS connection (connected=false, cert_valid=false). A legitimate brand extension would maintain valid HTTPS. The combination of brand impersonation and broken TLS is a strong phishing indicator, suggesting the site may be capturing credentials or payment data without proper encryption. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
The domain mimics a known consumer brand (Gymshark) under a suspicious TLD (.io) with no valid TLS certificate. This infrastructure profile is consistent with credential harvesting pages that present fake login or account forms. The page content could not be retrieved (empty page.html and page-text.txt), which may indicate bot-blocking or dynamic rendering used to evade automated scanners while serving malicious content to real users. (location: domain: gymsharkapps.io; metadata.json: tls fields)
hidden content
Page content files (page.html, page-text.txt, page-hidden.txt) are all empty despite the domain resolving and being scanned. This may indicate the site employs cloaking techniques — serving different content to crawlers/scanners versus real browsers or targeted victims, a common evasion technique used by phishing and malware distribution sites. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty))
curl https://api.brin.sh/domain/gymsharkapps.ioCommon questions teams ask before deciding whether to use this domain in agent workflows.
gymsharkapps.io currently scores 46/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.