Is sex-masry.com safe?

suspiciousmedium confidence
48/100

context safety score

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

identity
90
behavior
80
content
27
graph
30

6 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

social engineering

Video title 'محور شراميط مصر في غروب واحد يمكن تشوف صورة اختك في الفيديوا الحق نفسك' (translation: 'Egyptian women in one group, you might see your sister's photo in the videos, watch yourself') uses fear and social pressure to manipulate users into clicking by implying a family member's intimate images may be exposed. This is a classic social engineering lure. (location: page.html:115, page-text.txt:89)

medium

social engineering

Third-party ad manager script loaded from 'https://js.wpadmngr.com/static/adManager.js' with data-admpid='204773'. External ad network scripts are a common vector for malvertising, drive-by downloads, and redirects to malicious sites outside the control of the host domain. (location: page.html:755)

medium

social engineering

Age verification popup is implemented entirely client-side using a cookie (kt_agecheck). There is no server-side enforcement — the gate is trivially bypassed by setting or deleting the cookie. This creates a false sense of compliance and may be used to legitimize the site while providing no real age barrier, potentially facilitating exposure of minors to harmful content. (location: page.html:806-840)

low

hidden content

Thumbnail images are initially rendered as a 1x1 transparent GIF (data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7) and only loaded via lazy-loading from external URLs. While this is a standard performance pattern, it means the actual image content is deferred and not directly scannable in the static HTML, potentially obscuring the real visual content of thumbnails from automated scanners. (location: page.html:96,117,138 (and throughout))

high

social engineering

Multiple video titles reference non-consensual scenarios including coercion ('اخي يجبرني العب بزوبره' — 'my brother forces me'), incest themes, and content framed around minors ('مراهقة' — 'teenager', 'الصغيرة' — 'the young one'). These titles are used as clickbait to lure users with taboo/illegal content framing, which is a social engineering technique to drive engagement and normalize harmful content. (location: page.html:379,400,463)

API

curl https://api.brin.sh/domain/sex-masry.com

FAQ: how to interpret this assessment

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

Is sex-masry.com safe for AI agents to use?

sex-masry.com currently scores 48/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.

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.