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
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Popunder/tabunder ad system with multiple third-party redirect chains including liguhayrhe.com, online-hd.amazingcontent.site, and go.rmhfrtnd.com. The popunder is hardcoded to fire on nearly every click interaction (frequency set to 999999 or 1 per session) and silently opens new tabs/windows to undisclosed destinations without user awareness. (location: page.html:line 79-433, script blocks configuring popunder spotId 25982 and 90595)
malicious redirect
The 'See All Videos' header button (id='header-redirect') redirects users to vxxx.com instead of staying on the site. The link is visually presented as a site navigation element but silently navigates users off-site. (location: page.html:line 1121)
social engineering
Age-verification bypass: campaign traffic from affiliate sources (isBravo, isDonny) silently sets localStorage '_agv'=1 to skip age gate, allowing users under 18 to bypass age checks without performing any actual verification. This is deceptive manipulation of site safety controls. (location: page.html:lines 221-226 and 42-43)
social engineering
In-player button dynamically swapped via date-gated JavaScript to display 'FULL VIDEO HERE' leading to fhgte.com with UTM parameter 'utm_campaign=ai.KBZ', creating false impression of full video access. Button text and destination change silently based on date conditions. (location: page.html:lines 963-968, page-text.txt:lines 887-892)
hidden content
Large base64-encoded JavaScript payloads in variables cGAm2MphS and fqp3VeZWI embedded directly in the page body. These contain obfuscated ad configuration data including VAST endpoint (vstvstsΠ°.com), TDS routing (bts.red12flyw2.site), and push notification subscription URLs (notification.tubecup.net) that are not visible to users. (location: page.html:lines 79-80)
obfuscated code
Minified and obfuscated JavaScript loader in the inline script block that dynamically injects ad scripts from /tkfupescd8/ path using randomized filenames (nrwo8f8mlq.js, 01rz1lwg3w.js, 0zz3y6t33n.js, kb0k6usydf.js). The loader uses Symbol.iterator and toPrimitive pattern obfuscation to obscure its function. (location: page.html:line 84)
hidden content
Client Hints delegation header delegates detailed browser fingerprint data (sec-ch-ua, sec-ch-ua-bitness, sec-ch-ua-arch, sec-ch-ua-model, sec-ch-ua-platform, sec-ch-ua-platform-version, sec-ch-ua-full-version, sec-ch-ua-mobile) to tsyndicate.com, enabling covert device fingerprinting by a third-party ad network without user disclosure. (location: page.html:line 40)
malicious redirect
Geo-targeted hardlink injection: users in US/DE/NL/FR/GB are silently redirected to vbuidencestures.com (suspicious domain) labeled 'πAI SEX CHAT', while other geos are redirected to dpnode.top labeled 'πAI UNDRESS'. Both use obfuscated UUID-style paths and affiliate tracking, with no clear disclosure of destination. (location: page.html:lines 1130-1161)
social engineering
Yandex Metrika (ym) tracker is loaded from mc.yandex.ru alongside Google Tag Manager, collecting behavioral data including campaign source, referrer, page type, and magma_source cookie values. The Yandex tracker is a Russian analytics service collecting data on all visitors including those from Western countries, without prominent disclosure. (location: page.html:lines 30-35)
hidden content
window.addEventListener and document.addEventListener are monkey-patched to intercept and log all event listeners into a global '_eventsControl' list. This enables ad/tracking scripts to monitor and potentially remove all user-triggered events, and provides a backdoor to inspect all registered event handlers. (location: page.html:lines 888-913)
curl https://api.brin.sh/domain/porntop.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
porntop.com 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.