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
phishing
1 deceptive links where visible host does not match destination host
social engineering
The page title and metadata reference 'UZPORNO.RU' while the actual domain is uzporno.site. This deliberate domain name mismatch is used throughout the page (title, h1, footer, JSON-LD schema, canonical meta, copyright) to trade on the reputation of the .ru domain while operating from a .site TLD, misleading users about the true site identity. (location: page.html:8, page.html:19-22, page.html:34, page.html:111, page.html:1581)
hidden content
The page contains a hidden court-blocking overlay element with class 'rkn-stop' and 'rkn-stop-black' that displays 'САЙТ ЗАБЛОКИРОВАН ПО РЕШЕНИЮ СУДА' (SITE BLOCKED BY COURT ORDER). This is rendered visually but likely hidden via CSS to circumvent blocking enforcement while still serving content to users bypassing Russian RKN censorship. The body class 'rkn-class' combined with these overlay divs suggests CSS toggling of block visibility. (location: page.html:72-74)
social engineering
Multiple comment-section entries from the same IP range (188.113.246.*) posted within minutes of each other repeatedly promote the Telegram channel 'bingooo696', describing it as a reliable paid channel with exclusive content. This is coordinated astroturfing/fake reviews to drive traffic to an unvetted external Telegram channel, a common vector for scams and further content distribution. (location: page.html:1443-1478, page-text.txt:1373-1406)
social engineering
A user comment posted under the name 'Nigor' from IP 188.113.239.* publicly posts a personal phone number ('91 205 00 85') soliciting contact, appearing in two consecutive comments on different video pages. This is consistent with sex-work solicitation or human trafficking lure tactics embedded in public comment sections. (location: page.html:1488-1504, page-text.txt:1418-1433)
brand impersonation
The site operates at uzporno.site but consistently brands itself as 'UZPORNO.RU' throughout all metadata, JSON-LD structured data, page title, h1 heading, footer copyright, and canonical link. The .ru domain appears to be the original/blocked domain; this .site clone impersonates that brand to retain user trust while evading Russian court blocking orders. (location: page.html:8, page.html:19, page.html:34, page.html:111, page.html:1581)
malicious redirect
The site loads an external ad manager script from 'js.wpadmngr.com/static/adManager.js' with data-admpid='393983'. This third-party ad network is known to serve aggressive/redirecting ad content and popunders. Combined with a 'KernelTeamImageRotator.js' script invoked on page load, these scripts can trigger unsolicited redirects, popups, or drive-by download attempts on visitor browsers. (location: page.html:1613, page.html:24-25)
hidden content
Email address in the footer is obfuscated using Cloudflare's email protection encoding: the mailto link uses '/cdn-cgi/l/email-protection' with encoded data-cfemail attribute, and a companion script '/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js' is loaded to decode it client-side. While Cloudflare email obfuscation is a standard anti-spam measure, the pattern obscures the actual contact email from automated scanners. (location: page.html:1586, page.html:1613)
social engineering
The site prominently promotes a Telegram bot '@uzpornoobmenbot' for users to submit videos, creating a pipeline for collecting and distributing non-consensual intimate imagery (NCII). The framing as a legitimate 'upload' feature normalises participation in potential revenge porn or illicit content distribution. Multiple video titles explicitly describe leaked/stolen ('слив') content from named real individuals (e.g., 'Nozephry', 'Алиева Нигора 1nigow_', 'Зарина Усманова', 'Yusupov Jafar'), indicating actual non-consensual exposure of identifiable persons. (location: page.html:1583, page.html:92, page-text.txt:48, page-text.txt:191, page-text.txt:946, page-text.txt:1076)
social engineering
The footer link to an external site 'pornobolt.net' is embedded in a promotional block styled as a personal recommendation ('Азиз, Ислам и Сардор давно дрочат на порнуху от Pornobolt'). This is a covert affiliate/traffic exchange link using fake personal endorsement framing to drive outbound traffic. (location: page.html:106)
curl https://api.brin.sh/domain/uzporno.siteCommon questions teams ask before deciding whether to use this domain in agent workflows.
uzporno.site 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.