context safety score
A score of 44/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
malicious redirect
script/meta redirect patterns detected in page source
brand impersonation
The page at markedoneofthe.com (133-day-old domain) replicates the Google search homepage UI — including the Google logo (via a large base64-encoded PNG sized to 272x92px matching Google's logo dimensions), a rounded search bar styled identically to Google's, a blue search button using Google's brand color #4285f4, and Google font (Nunito via Google Fonts) — while hosted on an unrelated domain with no affiliation to Google. (location: page.html:27-35, page.html:147-149, page.html:56-64)
social engineering
The page presents itself as a browser 'New Tab' replacement page (title is 'New Tab'), impersonating a default browser new tab experience. This is a common technique used by browser hijackers and adware extensions to redirect users to attacker-controlled pages while appearing as a trusted system UI. The page collects userAgent data on load (navigator.userAgent captured into a variable) and presents shopping brand shortcut links, suggesting monetization via affiliate traffic diversion or data collection. (location: page.html:9, page.html:238)
malicious redirect
The search bar redirects user queries to 'https://google.com/search?q=' + searchKey via window.location.href, which superficially appears benign but is operated from a non-Google domain masquerading as Google. The redirect logic is implemented on an impersonation page, meaning any search interaction occurs in an attacker-controlled context before the redirect. Additionally, the userAgent is silently captured (encodeURIComponent(navigator.userAgent)) during DOMContentLoaded, which could be used for fingerprinting or exfiltration. (location: page.html:299-304, page.html:238)
hidden content
The page contains a large base64-encoded inline image (data:image/png;base64,...) embedded in the search icon element. This obfuscates what image is actually being displayed and prevents straightforward URL-based analysis. While likely the Google search icon, embedding it as base64 avoids external URL detection and makes automated content inspection harder. The page-hidden.txt file is empty, indicating no CSS-hidden text was extracted, but the base64 blob warrants flagging. (location: page.html:147)
curl https://api.brin.sh/domain/markedoneofthe.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
markedoneofthe.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.