context safety score
A score of 43/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
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
All outbound navigation links are routed through a base64-encoding redirect proxy at /go.php?url=<btoa(href)>. This obfuscates the true destination from users and security tools, and allows the site operator to silently change redirect targets server-side without updating page content. (location: page.html:561 — createLink() function: link.href = 'https://pornzog.com/go.php?url='+btoa(href))
malicious redirect
Banner ads are loaded from the suspicious third-party domain 'whoisezh.com' (name designed to mimic a 'whois' lookup service) via dynamically injected iframes. The domain name is deceptive and the ad content is refreshed automatically every 6 minutes, continuously exposing users to potentially malicious ad payloads. (location: page.html:162 — runExo(): url = 'https://whoisezh.com/in/912/?source=&spot_id=...')
malicious redirect
The Trafficstars/Clickadilla ad tag configuration includes 'tabunder:true', which causes a new browser tab to silently open a third-party URL (poloptrex.com) behind the current window without any user interaction or consent. This is a known malvertising technique. (location: page.html:76 — window['_sx6iuez9w4'] ad config: 'tabunder':true, banner_ssp_url: 'https://poloptrex.com/get')
malicious redirect
Inpage push-notification ad spot uses proxy_domain 'boannred.com', auction_url 'iloptrex.com', and ip_check_url 'nereserv.com' — all low-reputation or unrecognized domains used as ad infrastructure intermediaries. These domains may perform geo-targeted redirects or serve malicious payloads. (location: page.html:76 — _sx6iuez9w4 inpage spot config: proxy_domain, auction_url, ip_check_url fields)
social engineering
A blinking green dot animation is used alongside 'LIVE SEX CAMS' navigation links to create a false impression of a live streaming indicator, manipulating users into believing there are real people online waiting. This is a deceptive UI pattern designed to increase clicks to external cam sites. (location: page.html:510-532 — .green-blink-dot CSS animation applied to LIVE SEX CAMS header links)
social engineering
Time-conditional link swapping logic uses date thresholds (2026/03/14, 2026/02/22) to show different affiliate destinations (livehdcams.net vs ctwmsg.com/jasmin, track.lovescape.link vs ctwmsg.com/cutiesai) without user awareness. This obscures the actual destination and allows silent replacement of affiliate targets. (location: page.html:209-251 — hl1/hl2 date-conditional link assignment blocks)
hidden content
Yandex Metrika tracking pixel is loaded with webvisor:true (session recording enabled), tracking all user clicks and mouse movements. The tracking image is positioned at left:-9999px to be invisible to users. While common for analytics, the combination of full session recording and hidden pixel constitutes covert surveillance. (location: page.html:1019 — <noscript><div><img src='https://mc.yandex.ru/watch/33861189' style='position:absolute; left:-9999px;')
hidden content
The ad configuration object uses a non-descriptive obfuscated window key '_sx6iuez9w4' and loads scripts from a path '/0pexualpnq/' with randomized-looking filenames (rptx7nc7w8.js, uc51ptlcuw.js, 2xpw8hfi55.js, 35vh3pspfg.js). This path obfuscation is a common technique to evade ad-blocker and security scanner detection. (location: page.html:76-78 — window['_sx6iuez9w4'] and script src='/0pexualpnq/rptx7nc7w8.js')
curl https://api.brin.sh/domain/pornzog.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
pornzog.com currently scores 43/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.