context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
phishing
The domain skcrtxr.com hosts a login page branded as 'Roxot | SSO' with email and password credential input fields. The domain name (skcrtxr.com) is a random-looking, non-descriptive string with no apparent relation to the 'Roxot' brand, which is a common phishing pattern where attackers use throwaway domains to host credential-harvesting login pages mimicking legitimate services. (location: https://skcrtxr.com — page.html:9, page.html:33)
credential harvesting
The page presents a login form (id='login-form') that POSTs username (_username) and password (_password) fields to /account/login on the same suspicious domain. The domain skcrtxr.com has no established brand identity yet hosts a full SSO login interface, strongly indicating credentials entered here are harvested by a threat actor rather than authenticating to a legitimate service. (location: page.html:39-52)
brand impersonation
The page claims to be 'Roxot | SSO' and renders a Roxot SVG logo, but is served from the unrelated domain skcrtxr.com. If Roxot is a legitimate company, this constitutes brand impersonation by hosting a fake SSO portal under a deceptive domain to trick users into believing they are authenticating with the real Roxot platform. (location: page.html:9 (title), page.html:33 (logo img src='/assets/img/roxot.svg'))
curl https://api.brin.sh/domain/skcrtxr.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
skcrtxr.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.