context safety score
A score of 42/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
js obfuscation
Obfuscated document.write with encoded content
brand impersonation
The site uses 'TW' branding throughout (TW Pornstars, twpornstars.com, twgays.com, twmilf.com, twonfans.com, twtiktoks.com, etc.) with a disclaimer stating it uses the Twitter API but is not endorsed by Twitter. The 'TW' prefix across the entire domain network mimics Twitter/X branding to imply official association while aggregating and redistributing Twitter content commercially. (location: page.html:14-16, page.html:758, navbar links lines 65-89)
malicious redirect
A popunder ad script from prscripts.com is loaded with a 360-second (6-minute) delay using a cookie-based timing mechanism to evade immediate detection. The advloader framework dynamically injects scripts and tracks visit timing via the 'a_delay' cookie to trigger delayed popunder redirects after the user has been on the site for a set period. (location: page.html:874-880, page-text.txt:765-771)
malicious redirect
Two scripts are loaded from divingamends.com, an unrecognized third-party ad domain with obfuscated hash-based filenames (8bc5a4feb5928590482f8376a67e6ba5.js and 35fd862a211871130a720a8040aa9aa6.js). This domain is not a known reputable ad network and the hash-named scripts obscure their true purpose, indicating potential drive-by redirect or malvertising payload delivery. (location: page.html:882)
hidden content
A hidden 1x1 pixel iframe is injected by a Cloudflare challenge script using absolute positioning (top:0, left:0, visibility:hidden, border:none). While ostensibly a Cloudflare bot-challenge mechanism, the inline script dynamically creates the iframe and injects further script content into it, which could be used to load content invisible to users. (location: page.html:899, page-text.txt:790)
social engineering
Thumbnail content includes engagement-bait post titles designed to solicit user interaction, such as 'best comment wins the full vid', 'Let me see your tits and links in the replies', and 'Comment if you'd eat my ass'. These are social engineering tactics to drive user engagement and link sharing on the platform. (location: page.html:522, page.html:483-490, page.html:314)
curl https://api.brin.sh/domain/twpornstars.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
twpornstars.com currently scores 42/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.