context safety score
A score of 39/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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Popup/popunder ad script from a.pemsrv.com (ExoClick ad network) is configured with new_tab:true, popup_fallback:true, and trigger_method:2, meaning clicks on images or titles trigger redirects to third-party ad destinations. This is a known aggressive ad network used on adult sites to redirect users to potentially malicious or deceptive pages. (location: page.html:1467-1493 (inline script, adConfig with ads_host: a.pemsrv.com, idzone: 4644858))
malicious redirect
Frame-busting script forces top-level navigation when page is loaded inside an iframe: top.location.href = document.location.href. While sometimes legitimate, this can be abused to hijack navigation context or break security sandboxing in agent/browser automation environments. (location: page.html:36-39)
obfuscated code
All script tags use a non-standard type attribute value '50ad13a56c9602bb991c710a-text/javascript' instead of 'text/javascript'. This is a Cloudflare Rocket Loader obfuscation technique that defers script execution. Scripts are loaded via /cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js which rewrites the type attribute — however this pattern can also be used to hide script execution from naive scanners. (location: page.html:14,19,23,35,1457-1462,1467)
hidden content
Two tag URLs use MD5-style hash slugs instead of human-readable Arabic text, while displaying normal Arabic labels. The URLs /tag/0d501a71c88574eee616222fc994250f/ and /tag/66bd9de2affb3ce38ac864a307ef0a9f/ are obfuscated paths that do not match the visible tag names 'السكس' and 'سكس', which may indicate tracking tokens or cloaked redirect paths. (location: page.html:1382-1386)
social engineering
Site includes a navigation link to an external domain sexumahat.com opened in a new tab (target=_blank), directing users off-site to another adult property without warning. Combined with the popup ad network, this creates a multi-vector user redirection pattern typical of traffic monetization schemes that may expose users to malicious third-party content. (location: page.html:188)
curl https://api.brin.sh/domain/mlookalporno.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
mlookalporno.com currently scores 39/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.