context safety score
A score of 45/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
obfuscated code
Obfuscated popunder ad script using base64-encoded URLs (atob decoding) and a hardcoded expiry timestamp to dynamically inject external scripts. The script uses an IIFE with encoded CDN endpoints ('d3d3LmNkbjRhZHMuY29tL0Qvb3NpZ21hLm1pbi5qcw==' decoding to 'www.cdn4ads.com/D/osigma.min.js' and a CloudFront CSS URL), anti-freeze logic, and fallback loading — a common pattern for concealing malicious or unwanted ad payload delivery. (location: page.html:113)
malicious redirect
The obfuscated popunder script (page.html:113) uses siteId computed as 609+411*872-67+4724228=362538 with popunder configuration, dynamically loading scripts from www.cdn4ads.com and a CloudFront endpoint. Popunder ad networks are routinely exploited to redirect users to phishing pages, tech-support scams, or malware distribution sites without user consent. (location: page.html:113)
social engineering
Navigation menu link 'Desi Kahani' points to external domain https://www.indiansexkahani.com/ without disclosure, silently routing users off-site. Cross-site navigation via embedded menu items to undisclosed affiliate or partner sites is a common social engineering vector on adult content platforms. (location: page.html:130)
social engineering
Prominent animated gradient banner 'KaamDesi - Free Desi Porn Videos' links to external domain https://kaamdesi.com/ styled to appear as site-native content, designed to lure clicks to an undisclosed third-party site. No affiliate disclosure or external-link indicator is present. (location: page.html:179)
hidden content
A Webmaster affiliate/recruitment link in the footer uses visually styled inline CSS to make it appear as a button/badge, obfuscating its nature as a webmaster program recruitment link. This is a common technique on adult sites to recruit traffic resellers without clear disclosure. (location: page.html:1085)
hidden content
Third-party visitor counter script loaded from //widget.supercounters.com/ssl/online_t.js tracks user presence and exposes visit data to an external analytics provider without user consent notice, operating as a silent tracking beacon. (location: page.html:1090)
curl https://api.brin.sh/domain/fsiblog.ccCommon questions teams ask before deciding whether to use this domain in agent workflows.
fsiblog.cc currently scores 45/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.