context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
Theme path uses heavily obfuscated URL-encoded characters: '%2A%28%40%26%24%21%40KSADJ' used consistently across all theme asset paths (CSS, JS, ajax endpoint). This non-standard theme directory name obfuscates the theme identity and could conceal malicious code within theme files. (location: page.html:24,82,83,85,86,89,1267 - theme_ajaxurl and all theme asset hrefs)
hidden content
Commented-out advertisement blocks reference external domains 'ihaveporno.com' and 'ihaveporno3.com' with tracking redirect links (e.g. https://ihaveporno.com/lib/ref.php?https://t.ly/BSIoz, https://ihaveporno3.com/lib/ref.php?https://t.ly/lotto7777, https://ihaveporno3.com/lib/ref.php?https://t.ly/slot6666, https://ihaveporno3.com/lib/ref.php?https://t.ly/sa666, https://ihaveporno3.com/lib/ref.php?https://t.ly/ufafat). These hidden ad redirects point to gambling/lottery sites via URL shorteners, concealing the final destination. (location: page.html:1157-1170, 1308-1328)
malicious redirect
Commented-out ad blocks contain redirect links through 'ihaveporno.com/lib/ref.php' and 'ihaveporno3.com/lib/ref.php' acting as redirect proxies to shortened URLs (t.ly/BSIoz, t.ly/LM9jN, t.ly/G3xxS, t.ly/lotto7777, t.ly/slot6666, t.ly/sa666, t.ly/ufafat). These redirect chains obscure final landing pages — link labels suggest online gambling and lottery destinations, which are commonly associated with scam or phishing operations. (location: page.html:1158-1169, 1310-1326)
social engineering
The site explicitly promotes itself as a PornHub alternative ('PornHub ดูไม่ได้ แต่เว็บหนังโป๊พรฮับเราดูได้อย่างแน่นอน' — 'PornHub can't be watched but our PornHub-like site can definitely be watched'), leveraging the PornHub brand to attract users who are blocked from accessing the legitimate platform. This exploits brand recognition and user frustration to drive traffic. (location: page.html:32,38 - meta description)
brand impersonation
Site description explicitly references 'พรฮับ' (PornHub in Thai phonetic transliteration) and positions itself as a direct substitute for PornHub, implying equivalence or affiliation with the PornHub brand without authorization. The site is 'ihaveporn.net', not affiliated with PornHub. (location: page.html:32,38,42 - meta description and og:description tags)
hidden content
The page title element in the site header is marked 'is-hidden' via CSS class: <h1 id="site-title" class="is-hidden">. This hides the full site title from visual display while keeping it present in the DOM, a technique sometimes used to stuff keywords or content for crawlers/agents while hiding it from users. (location: page.html:108 - <h1 id="site-title" class="is-hidden">)
curl https://api.brin.sh/domain/ihaveporn.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
ihaveporn.net 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.