context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
brand impersonation
The page title is 'Dashboard' and meta description references 'CRM, CMS' admin theme, but the domain is fairdeal.live — a generic commercial-sounding domain hosting what appears to be a full admin panel application. The meta author tag 'Coderthemes' indicates a stolen or repurposed admin theme template being used to impersonate a legitimate dashboard/portal. The page loads an Angular app (app-root) with no visible branding, consistent with a spoofed login or admin portal. (location: page.html:3,9,10,50)
credential harvesting
The site serves a blank-rendered Angular SPA (page-text.txt is empty) with a full admin dashboard template (Coderthemes theme). The combination of an empty visible text layer, Angular app-root, and login.css stylesheet strongly suggests a credential harvesting login page that renders client-side only — evading static text analysis while presenting a login form to real users. (location: page.html:25,50,51)
phishing
The domain fairdeal.live hosts what appears to be a cloned or repurposed admin/CRM dashboard template (Coderthemes) with no visible page content in static extraction (page-text.txt is nearly empty). This is a classic phishing site pattern: a JavaScript-heavy SPA that renders a convincing interface only in the browser, avoiding detection by crawlers and static scanners. (location: page.html:50-51; page-text.txt:1-4)
malicious redirect
External JavaScript is loaded from speedcdn.io (not a well-known CDN) for 'flashphoner.bundle.min.js' — a WebRTC/streaming library. Loading opaque third-party JS from an unfamiliar CDN (speedcdn.io) on an admin/login page introduces significant supply-chain and redirect risk. This script executes before any page content and could intercept credentials or redirect users. (location: page.html:13-14)
hidden content
Multiple commented-out viewport meta tags and script references exist in the HTML source, including a commented-out HTTP (non-HTTPS) jQuery UI reference from ajax.googleapis.com. While individually low-risk, the pattern of multiple commented-out resource tags suggests iterative evasion testing or template remnants used to obscure the page's true purpose. (location: page-hidden.txt:1-17)
curl https://api.brin.sh/domain/fairdeal.liveCommon questions teams ask before deciding whether to use this domain in agent workflows.
fairdeal.live currently scores 39/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.