Is yesporn.vip safe?

suspiciouslow confidence
43/100

context safety score

A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
100
behavior
100
content
0
graph
30

9 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

cloaking

Page loads content in transparent or zero-size iframe overlay

high

malicious redirect

Third-party script loaded from pasttable.com using obfuscated path with escaped forward slashes ("\/\/pasttable.com\/cID.9q6Obz2O5clXSiW...") and dynamically injected into the DOM. This pattern is characteristic of ad-fraud, popup, or drive-by redirect networks. (location: page.html:1655, page-text.txt:1605)

high

obfuscated code

Script from fangmoonlight.com loaded inline: '//fangmoonlight.com/64/fc/d5/64fcd576b2001131a9761227e458c4d3.js'. The domain name and hash-like path are typical of ad-injector or malvertising infrastructure. No attribution or description is present. (location: page.html:1630)

medium

malicious redirect

Third-party affiliate link with encoded tracking parameters redirecting through ggptnetwork.com to an 'AI Cuckold' campaign: utm_campaign=AI+Cuckold. The URL contains UTM tracking and leads to an external ad network, potentially a gateway to deceptive content. (location: page.html:69)

medium

social engineering

Header navigation link labeled 'Join Telegram' points to a Telegram invite link (https://t.me/+xf80qlGHH_9kNWY0), a common social engineering vector used to move users to unmoderated channels for scams, malware distribution, or credential harvesting. (location: page.html:53)

medium

malicious redirect

Affiliate link to network.nutaku.net with encoded 'ats' tracking token redirects through a base64-encoded parameter chain, consistent with cloaked affiliate redirect chains that may lead to deceptive landing pages. (location: page.html:73)

medium

hidden content

Commented-out popup ad code in page source referencing cdn.sellspirev.com and an interstitial ad from cdn.tsyndicate.com. These are disabled but present, suggesting the site actively experiments with aggressive popup/interstitial ad injectors that may be re-enabled. (location: page-hidden.txt:7-18, page.html:1625-1671)

low

brand impersonation

The site hosts content under channels named 'Brazzers', 'RealityKings', 'Vixen', and 'pureTaboo' — well-known commercial adult studios. Hosting and distributing their content without authorization constitutes brand impersonation and potential copyright piracy. (location: page.html:305-308, page.html:1246-1328)

API

curl https://api.brin.sh/domain/yesporn.vip

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is yesporn.vip safe for AI agents to use?

yesporn.vip 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.

How should I interpret the score and verdict?

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.

How does brin compute this domain score?

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.

What do identity, behavior, content, and graph mean for this domain?

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.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

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.

Can I rely on a safe verdict as a full security guarantee?

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.

When should I re-check before using an entity?

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.

Last Scanned

March 4, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Disclaimer

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.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.