context safety score
A score of 56/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
The page is served from dragon222site.org but all canonical URLs, Open Graph metadata, static assets, scripts, and links point exclusively to shortener.amplittlegiant.com. The scanned domain acts as a disguised front-end that loads all content and functionality from a separate URL shortener platform, enabling the operator to redirect any shortened link to arbitrary destinations without the visitor being aware of the true delivery domain. (location: page.html: meta og:url (line 12), link canonical (line 23), all script/link src attributes, appurl JS variable (line 29))
brand impersonation
The page presents itself as a generic 'domain working' confirmation page while silently operating as an active URL shortener service (shortener.amplittlegiant.com). The neutral title 'Great! Your domain is working.' masks the true purpose of the infrastructure, which can be used to shorten and disguise links for phishing or malware distribution campaigns. (location: page.html: <title> line 8, <h6> line 41, og:title line 13)
malicious redirect
dragon222site.org is a custom domain pointed at a URL shortener platform (shortener.amplittlegiant.com). URL shorteners are a well-established technique for obfuscating the final destination of malicious links. The domain is only 296 days old, was registered without privacy redaction, and hosts no legitimate business content — consistent with a purpose-built redirect/phishing infrastructure domain. (location: metadata.json: domain dragon222site.org, page.html lines 42-43 describing shortening branded links)
curl https://api.brin.sh/domain/dragon222site.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dragon222site.org currently scores 56/100 with a caution 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.