context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The page is served from aeae888.com but displays a Cloudflare block page claiming the user is unable to access 'nxguarder06.com'. The page title reads 'Attention Required! | Cloudflare' and uses Cloudflare's exact error page markup, CSS, and messaging verbatim — mimicking a legitimate Cloudflare security challenge. The actual domain (aeae888.com) has no relationship to Cloudflare or nxguarder06.com, indicating the Cloudflare UI is being impersonated to appear trustworthy. (location: page.html:7, page.html:37)
social engineering
The page instructs users to 'email the site owner' and include details about what they were doing, framing a deceptive block page as a legitimate security measure. This is designed to elicit user action and information disclosure under the guise of resolving a Cloudflare block, when the page is actually hosted on a suspicious domain (aeae888.com) unrelated to the displayed content. (location: page.html:59-62, page-text.txt:29-31)
malicious redirect
The page is hosted on aeae888.com (224 days old) but displays content referencing a completely different domain, nxguarder06.com. This domain mismatch strongly suggests a redirect chain or cloaking setup where the user is delivered a fake Cloudflare error from one domain while being told they are blocked from another, consistent with a traffic redirection or cloaking scheme. (location: metadata.json (domain: aeae888.com), page.html:37)
hidden content
The page includes a hidden IP address element ('34.34.233.216') inside a span with class 'hidden', revealed only on button click. Additionally, the 'cf-footer-item-ip' span is initially hidden via CSS class and only shown via JavaScript. While this mirrors real Cloudflare behavior, on an impersonation page this mechanism could be used to collect or display harvested IP data to deceive users. (location: page.html:70-75)
curl https://api.brin.sh/domain/aeae888.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
aeae888.com currently scores 44/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.