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
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The domain appbaqend.com hosts a pixel-perfect clone of the Appodeal sign-in page (title: 'Sign In | Appodeal Intelligent Ad Mediation', logo, layout, and branding identical to appodeal.com). The domain name 'appbaqend' does not belong to Appodeal Inc. and is a typosquat/impersonation of the legitimate 'appodeal' brand. (location: https://appbaqend.com — page title, navbar logo (alt='APPODEAL'), and overall page structure)
credential harvesting
A login form targeting business email and password is served on the impersonating domain. Form POSTs to /signin on appbaqend.com, not to appodeal.com. Submitted credentials (business email + password) would be captured by the attacker controlling this domain. (location: page.html — <form action='/signin' method='post'> with inputs user[email] and user[password])
phishing
The page combines brand impersonation with a credential-harvesting login form and 'Sign Up' flow, constituting a full phishing site targeting Appodeal customers and developers. The domain is ~8 years old (2849 days), reducing typical new-domain phishing signals, which may allow it to evade blocklists — confirmed not currently blocklisted. (location: https://appbaqend.com (full page))
social engineering
The page reproduces legitimate Appodeal UI text including 'Remind password', 'Not yet registered? Sign Up', footer copyright '© 2026 Appodeal Inc.', Terms of Service, Privacy Policy, and SDK License Agreement links — all designed to build false trust and lower victim suspicion before credential submission. (location: page-text.txt — footer and form helper text; page.html — footer links)
curl https://api.brin.sh/domain/appbaqend.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
appbaqend.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.