context safety score
A score of 27/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
phishing
1 deceptive links where visible host does not match destination host
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The domain earringsbyamy.co.uk is serving content entirely unrelated to its registered identity. The page presents itself as 'sieusex.uk', a Vietnamese adult content site, while the domain name suggests a legitimate UK jewellery business. All canonical URLs, og:url, og:site_name, schema.org data, and branding point to webcottages.co.uk and sieusex.uk — completely different entities. This is a classic domain hijack/repurposing attack where a trusted aged domain (14833 days old) is used to host malicious/spam content under a deceptive identity. (location: page.html:9, page.html:12, page.html:18-19, page.html:239-243)
malicious redirect
JavaScript pop-under script fires on any user click and opens https://oopen88.xyz/sieusexopen88 in a new tab. The script uses localStorage throttling (1-hour cooldown, key 'ok83866_last') to evade detection and rate-limit the redirect. The target domain oopen88.xyz is an unrelated third-party site consistent with malvertising or traffic monetisation networks. This redirect fires silently without user consent on first interaction. (location: page.html:826-865)
malicious redirect
A floating banner ad element links to https://oopen88.xyz/sieusexopen88 via an anchor tag with rel=nofollow. The banner image uses alt text 'ok83866' matching the localStorage key used in the pop-under script, indicating coordinated ad-fraud infrastructure. The banner is rendered fixed at z-index:9999 to maximise visibility and click likelihood. (location: page.html:276, page.html:968)
hidden content
A div with class 'hidden' in the header contains the text 'sieusex.uk', which is not visible to normal users but is present in the DOM. This is used to embed brand signals for the actual operating site while the domain appears to be earringsbyamy.co.uk, a technique used to confuse crawlers, AI agents, and security scanners about the true identity of the site. (location: page.html:239)
brand impersonation
The canonical link tag points to https://webcottages.co.uk/ and the schema.org JSON-LD identifies the organisation as 'sieusex.uk' with @id referencing webcottages.co.uk. The page is served from earringsbyamy.co.uk but masquerades as webcottages.co.uk in all machine-readable metadata. This deceives search engines, AI crawlers, and link-preview agents into attributing webcottages.co.uk content and reputation to earringsbyamy.co.uk. (location: page.html:12, page.html:23)
social engineering
Multiple video thumbnails use real-sounding Vietnamese personal names combined with birth years (e.g. '2k4', '2k5', '2k6', '2k7', '2k8') and institutional affiliations (named universities, companies) in titles framing the content as non-consensually leaked private recordings ('lộ clip'). This is a social engineering pattern designed to exploit voyeuristic and sensationalist impulses to drive clicks, and may also constitute non-consensual intimate image sharing as a lure. (location: page.html:382-692)
obfuscated code
Custom b2a/a2b base64 encoding functions and b64e/b64d wrappers are defined inline and used extensively by the Ad Inserter plugin infrastructure to dynamically decode and inject ad code blocks at runtime. The pattern of storing ad payloads as base64 in data-code attributes and decoding them on-demand (via b64d/atob) is a known obfuscation technique to hide ad content from static scanners and to allow dynamic payload swapping without modifying visible HTML. (location: page.html:1001-1003, page-text.txt:647-649)
hidden content
The Ad Inserter plugin (ai-viewports CSS classes) uses CSS rules to set multiple viewport-targeted elements to display:none by default, with content conditionally revealed via JavaScript. Combined with base64-encoded data-code attributes, this creates a mechanism where ad or redirect payloads can be hidden from static analysis and only rendered in specific browser environments, bypassing content security scanners. (location: page.html:215-233)
curl https://api.brin.sh/domain/earringsbyamy.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
earringsbyamy.co.uk currently scores 27/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.