context safety score
A score of 46/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 conditionally redirects based on referrer or user-agent
obfuscated code
Navigation links and external URLs are systematically base64-encoded in data-obfs attributes and decoded at runtime via an externally loaded obfs.js script. This conceals link destinations from static analysis and security scanners. (location: page.html: multiple elements with data-obfs attributes; assets.tukif.porn/assets/default/js/excluded/obfs/obfs.js)
malicious redirect
A popunder ad mechanism is configured for both mobile and tablet users, triggered on video thumbnail clicks. It loads an external ad feed from feex.tukif.porn and dispatches to plx.tukif.porn pool links, redirecting users to third-party destinations without clear disclosure. The script pu.js handles popunder execution. (location: page-text.txt line 126: module.promo_tool config; assets.tukif.porn/assets/default/js/excluded/pu.js)
malicious redirect
An external third-party affiliate link to tools.sedulove.com is loaded via a JSON data fetch to populate a webcam/dating widget, redirecting users to a dating/hookup affiliate platform without prominent disclosure. (location: page-text.txt line 80: JSON data blob referencing https://tools.sedulove.com/xml.php with affiliate parameters)
hidden content
Several HTML comments reference placeholder content sections ('content here') and a commented-out history container div, indicating structural elements intentionally hidden from rendering. A Yandex Metrika tracking pixel is also hidden off-screen at left:-9999px via a noscript tag. (location: page-hidden.txt lines 5-13; page.html noscript Yandex Metrika img tag)
social engineering
The site uses an age verification disclaimer system with blurred content and prominent calls-to-action. By clicking 'ENTRER', users are coerced into accepting Terms and Conditions and a Privacy Policy. The disclaimer bypass sets long-lived cookies and integrates with an external age verification service (ageverif), nudging users to consent to data collection. (location: page.html lines 39-111: tkn_disclaimer_helper script; page-text.txt line 106)
curl https://api.brin.sh/domain/tukif.pornCommon questions teams ask before deciding whether to use this domain in agent workflows.
tukif.porn currently scores 46/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.