context safety score
A score of 32/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
phishing
Page impersonates PayPal login
malicious redirect
Two instances of SNSPAdManager pop-under ad scripts are embedded in the page, both configured to open https://go.gsrv.dev/pop.go?spaceid=11829029 and https://go.gsrv.dev/pop.go?spaceid=11829030 in new windows when any link is clicked. The scripts intercept all anchor clicks and redirect users to third-party ad networks without disclosure. The trafficPercentage values exceed 1.0 (set to 1.1 and 1.5), meaning the condition Math.random()>=trafficPercentage is always false and the pop fires on every qualifying click. An antiInspection flag is also present to evade detection tools. (location: page.html lines 331-556 and 564-915; page-text.txt lines 208-915)
social engineering
The page uses aggressive social engineering language to persuade users to register: 'we won't pressure you or try and trick you in any way with any charges once you become a member' — a reassurance pattern commonly used on sites that do impose hidden charges or upsell traps. The login/signup form is prominently placed in a dropdown overlay with autocomplete disabled, consistent with credential-harvesting UI patterns. (location: page.html line 155-167 (footer SEO text); page.html line 122 (login form))
credential harvesting
Login form posts credentials via AJAX to https://www.porntrex.com/ajax-login/ with autocomplete='off' on both username and password fields. While the domain matches, the autocomplete suppression combined with the pop-under ad infrastructure and third-party ad scripts (adsmediabox.com) creates an environment where session cookies and credentials could be intercepted or exfiltrated by injected third-party scripts. (location: page.html line 122 (<form action='https://www.porntrex.com/ajax-login/'>))
hidden content
A commented-out JavaScript redirect to https://landing.brazzersnetwork.com/?ats=... with encoded affiliate tracking parameters is present in the source. While currently commented out, it indicates previously active forced redirect logic that was simply disabled rather than removed, and could be re-enabled at any time. (location: page.html lines 270-273; page-text.txt lines 147-150)
malicious redirect
Third-party ad script loaded from https://adsmediabox.com/ads.js?z=233&ad_height=300 — adsmediabox.com is a third-party ad network with no content integrity guarantees. Loading arbitrary external JavaScript from this domain gives it full DOM access, the ability to modify links, exfiltrate cookies, and inject further redirects or malware. (location: page.html line 331)
curl https://api.brin.sh/domain/porntrex.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
porntrex.com currently scores 32/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.