context safety score
A score of 35/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
The scanned URL sedirkettering.co.uk serves content entirely belonging to mumtazrestvn.com. The canonical tag, all assets, all links, and the site identity point to mumtazrestvn.com, indicating sedirkettering.co.uk is a redirect/cloaking domain funneling users to a different site without disclosure. (location: page.html:11 - <link rel='canonical' href='https://mumtazrestvn.com/'/>)
malicious redirect
A popup script fires on user click and opens one of two gambling/affiliate URLs (jun8899.me or mb6688.me) in a new tab after a 10-second delay and then every 60 seconds. This is unsolicited pop-under/pop-up redirection to external gambling sites. (location: page.html:46-94 - popupConfig script block)
obfuscated code
A large heavily obfuscated JavaScript block is present inside an HTML comment labeled 'PUPUNDER'. It uses URI-encoded strings, character-code rotation, and dynamic script injection to load a pop-under ad network payload from bodybossmotivate.com and waust.at. The obfuscation is designed to evade static analysis. (location: page.html:37-40 - <!--PUPUNDER ... --> comment block containing decodeURI/charCodeAt obfuscated script)
hidden content
The PUPUNDER script block and a secondary banner script referencing vipads.live are wrapped inside HTML comments, concealing active JavaScript from casual inspection while still being parsed and executed by browsers. (location: page.html:37-45 - scripts embedded within HTML comment syntax)
hidden content
A hidden 1x1 pixel iframe is dynamically injected with visibility:hidden and position:absolute at top:0/left:0, used to load and execute Cloudflare challenge scripts covertly without user awareness. (location: page.html:683 - inline Cloudflare iframe injection script)
social engineering
Footer links disguise their true destination by using innocent-looking anchor text ('sex vietsub', 'sexnhat', 'clip sex') pointing to unrelated UK domains (sportatschool.org.uk, cocorugby.co.uk, rupalipalace.co.uk, samariacafe.net, cafekreol.com), suggesting link-farm SEO manipulation and potential traffic laundering to unrelated sites. (location: page.html:655-659 - footer 'Lien Ket' link section)
malicious redirect
Third-party ad scripts are loaded from bodybossmotivate.com and waust.at — domains associated with aggressive ad networks — with dynamic src injection and error/load callbacks (onerror/onload='jdzby(15)'), enabling redirects and tracking outside user control. (location: page.html:39 - <script async src='//bodybossmotivate.com/on.js'>)
hidden content
Thumbnail images use a transparent 1x1 GIF as the src and store the real image URL in data-original for lazy loading, which can be used to delay content classification and evade image-based content scanning. (location: page.html:259 and throughout - lazyload img tags with data:image/gif placeholder src)
curl https://api.brin.sh/domain/sedirkettering.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
sedirkettering.co.uk currently scores 35/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.