context safety score
A score of 38/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
obfuscated code
Multiple heavily obfuscated inline JavaScript blocks using character-code rotation encoding (Caesar-cipher-style string obfuscation with charCodeAt/fromCharCode transforms, encoded string arrays, and randomized URL parameter injection). These scripts conceal their true behavior and destination URLs, consistent with ad fraud, tracking, or malicious redirect infrastructure. (location: page.html:668, page.html:674 (inline <script> blocks))
malicious redirect
External script loaded from //appointeeivyspongy.com/aas/r45d/vki/1947372/d62cc807.js — a domain with no legitimate reputation, loaded asynchronously with data-cfasync='false' to bypass Cloudflare security scanning. The obfuscated wrapper scripts dynamically construct and manipulate URLs with injected random query parameters before redirecting, a pattern used in malvertising and forced redirect chains. (location: page.html:669)
malicious redirect
External script loaded from //bartererfaxtingling.com/in.js — another non-reputable third-party domain loaded asynchronously with data-cfasync='false'. The domain name is nonsensical/randomly generated in style, consistent with malvertising network infrastructure used for click fraud and redirect chains. (location: page.html:672)
malicious redirect
External script loaded from //appointeeivyspongy.com/bn.js — same suspicious domain as the first injected script, loading a second payload, consistent with a multi-stage ad/redirect network dropping multiple scripts to chain victims through redirect sequences. (location: page.html:675)
obfuscated code
The obfuscated scripts use localStorage access, dynamic script element injection (document.createElement('script')), randomized query string parameter generation, and URL manipulation to construct redirect targets at runtime. This prevents static analysis from identifying destination URLs and is a hallmark of malvertising obfuscation techniques. (location: page.html:668 (inline script using localStorage, dynamic URL construction, random param injection))
social engineering
Site presents content framed as amateur/leaked 'Pinay sex scandal' videos, using the word 'scandal' to imply non-consensual or illicitly obtained intimate content. This framing is commonly used to drive clicks on ad networks, increase engagement, and lure victims into clicking redirected ad links. (location: page.html:553-554, metadata.json (og:description), page-text.txt:327-328)
hidden content
Ad spot placeholder divs using data-cl-spot attributes (data-cl-spot='1889528', data-cl-spot='1869287') in both header mobile and footer areas are empty containers that load content dynamically from an ad network at runtime. These containers can inject arbitrary HTML/JS including popunders, redirect scripts, or credential-phishing overlays without appearing in the static HTML. (location: page.html:266, page.html:561, page.html:563)
curl https://api.brin.sh/domain/pinayot.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
pinayot.com currently scores 38/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.