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
obfuscated code
Large Base64-encoded blobs stored in JavaScript variables (cGAm2MphS, fqp3VeZWI) at page load. The variable named cGAm2MphS decodes to ad-server configuration referencing 'actman.obfuscated.js', explicitly naming obfuscation. The payload is loaded via a dynamically constructed script src '/livesmatter/holly7.10.13.bccb68bf9b7da5f3d8345aad076e917b.js' with a hash fingerprint, obscuring the actual ad engine being loaded. (location: page.html:64-66)
malicious redirect
Popunder/tabunder ad system is configured to open new tabs or windows on user interaction (clicks on video player, thumbnails, page body). The popunder engine uses spot_id 7854 and is bound to nearly the entire page UI including '.jwplayer', '.thumb', '.__bai-overlay', and 'body' (when nplimit=1). This silently redirects users to third-party ad networks without consent, including liguhayrhe.com and other traffic broker domains. (location: page.html:411-519, 846-854)
malicious redirect
Push notification subscription interstitial configured with a directLink to 'https://online-hd.amazingcontent.site/?tag_id=93577&cl=3&click=1' — a suspicious domain used as a fallback redirect when a user interacts with push notification prompts. This can redirect users to unknown/potentially malicious content outside the site. (location: page.html:68 (subInterstitialSettings.directLink))
social engineering
'UNLOCK PREMIUM' button (window._plBtnText) and 'FULL VIDEO HERE' CTA are dynamically injected over video content as an overlay (.__bai-overlay with z-index 99999). This deceptively implies a content gate to extract clicks and redirect users to affiliate adult subscription sites (fhgte.com, javhd.com, g2fame.com, 1passforallsites.com). The overlay covers the player to trick users into clicking affiliate links. (location: page.html:72-97)
social engineering
Top bar ad with text 'AI Undress. Make Anybody Naked. Upload Image Generate Video' with a 'TRY FREE' button links to nudeai.fun — a non-consensual AI image manipulation service promoted through deceptive free-trial framing targeting users in high-value GEOs (US, UK, DE, FR, etc.). (location: page.html:213-221)
social engineering
Tab link titled '🔥AI CUM SLUT' (hlink_1) links to s.traf-gold.online traffic broker for GEO-targeted users, and '🔥AI porn' linking to candyai.gg for others. These are deceptive tab-link ads using sensational/explicit titles to drive clicks to external affiliate/adult AI platforms. (location: page.html:108-130)
hidden content
The .partners-wrap CSS class is set to 'display: none' via an inline style block, hiding partner/affiliate link content from the visible page. This conceals partner tracking or link content from users and scanners while it may still be active in the DOM. (location: page.html:56-60)
obfuscated code
The ad tag loader script at '/ocbxu9zk8a/4dsew1ob5s.js' is loaded via a dynamically constructed call using an obfuscated random-looking path segment. The initialization object '_hncd91ha4r' contains full ad format configuration including push notification spots and interstitial redirect URLs, all encoded within a single window variable to evade static analysis. (location: page.html:68-70)
malicious redirect
The delegate-ch HTTP meta tag delegates sensitive client hint headers (sec-ch-ua, sec-ch-ua-platform, sec-ch-ua-full-version-list, sec-ch-ua-mobile, etc.) to tsyndicate.com — a third-party ad/traffic syndication domain. This allows tsyndicate.com to fingerprint users' browsers, OS, and device details without explicit user consent. (location: page.html:55)
malicious redirect
Yandex Metrika (mc.yandex.ru) analytics tag is loaded unconditionally for all non-Lighthouse user agents, sending browsing behavior, click maps, and session data to Yandex servers. For users in Western countries this constitutes cross-border data transfer to a Russian state-adjacent entity. (location: page.html:46-51)
hidden content
Ad configuration variables (window.EoCR4, window.vf_keys with site API keys, window._campControl, window._hl, window._h2) are embedded inline in the page script but never rendered visibly. They contain internal routing keys, site API keys (e.g. 'sU5aXD9iHnTnjvg6QZ2s7fkReMNpHqMgO8JFBybZ'), and traffic source tracking logic invisible to users. (location: page.html:23, 299-304)
curl https://api.brin.sh/domain/inporn.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
inporn.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.