context safety score
A score of 48/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
hidden content
Multiple CSS classes use display:none and responsive breakpoint rules to selectively hide and reveal content blocks (e.g., .bb_show_1 through .bb_show_5, .tx1–.tx6, #list_trader_header, .tag_hidde, .to_hidde). While primarily responsive design patterns, some of these conditionally hide ad and trader blocks from certain viewport sizes, obscuring ad delivery behavior from analysis. (location: page.html, CSS block lines 340–378, 643–661)
hidden content
Bot-detection JavaScript (is_bot_one function) checks navigator.userAgent against a large regex pattern of known crawlers, bots, and security scanners. Scripts loaded via load_js_fast are only delivered to non-bot visitors, allowing different content or ad payloads to be served to real users versus automated scanners or security tools. (location: page.html lines 1336–1367)
malicious redirect
The page links to https://go.theporndude.tv via a nav menu item labeled 'Tube'. This is an affiliate redirect/tracker URL (go.theporndude.tv) that routes through a third-party redirect service before landing on the destination. The use of a subdomain-based go. redirect obscures the final destination from users and automated scanners. (location: page.html line 1586, nav link: href='https://go.theporndude.tv')
hidden content
Ad slots use obfuscated third-party endpoints (aa.qwerty24.net) for both mobile and desktop ad delivery, with URLs parameterized by site type ('xvideo.site_index'). The qwerty24.net domain is an ad network intermediary with no transparent ownership, potentially serving malvertising payloads outside the site's control. (location: page.html lines 1046–1048, JS variables ads_url_mobile/ads_url_desktop/ads_url_desktop_one)
hidden content
The site prefetches and loads resources from cdnjs.work, a domain that mimics the legitimate cdnjs.cloudflare.com CDN. The .work TLD variant is a known typosquatting pattern used to serve malicious scripts under the appearance of a trusted CDN. (location: page.html line 1 (dns-prefetch href='https://cdnjs.work'))
curl https://api.brin.sh/domain/pornhat.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
pornhat.tv currently scores 48/100 with a suspicious verdict and medium 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.