context safety score
A score of 37/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
exfiltration
JavaScript intercepts form submissions to exfiltrate data
malicious redirect
Navigation menu contains affiliate/tracker redirect links to third-party domains via tracking URLs: 'https://madepr.net/in/?s=z0PLxQQ28JayQ4qB' (AI Porn), 'https://wasp-182b.com/resource?zones=1250' (TikTok Porn), and 'https://go.mavrtracktor.com?userId=be19743d859c5f2c8f0f9a3a05f710f9d532baa09d175b73f0d16a28e90dea14' (Live Sex). These are obfuscated affiliate trackers with user-identifying tokens that redirect users to unknown third-party destinations. (location: page.html:89-91, nav menu)
malicious redirect
Page dynamically loads scripts from third-party domains at runtime via deferred script injection: 'https://log.perfecttitspics.com/renderer/renderer.js', 'https://perfecttitspics.com/adengine.js', '//cdn.tsyndicate.com/sdk/v1/master.spot.js', 'https://a.magsrv.com/ad-provider.js'. These ad/tracking engines are injected after a 3-second delay to evade static analysis and can serve malicious payloads or redirect users. (location: page.html:49-53)
hidden content
The page fetches banner content from '/api/api.php?counter=N' and dynamically injects it into the DOM including executing any scripts contained within the fetched HTML. This server-side API endpoint can deliver arbitrary HTML/JS content that is invisible during static analysis, including hidden redirects, tracking pixels, or malicious scripts. (location: page.html:422-451)
hidden content
The page tracks user scroll behavior and visit counts via a 'visitCounter' cookie, and fires 'window.hptRdr.update()' when ad banner elements enter the viewport. The 'hptRdr' object is loaded from the external ad engine scripts and its behavior is opaque — it can trigger silent redirects or popunders based on visit frequency thresholds. (location: page.html:499, 558-559)
social engineering
Menu items use urgency/attention-grabbing symbols (⭕, 🔴) and labels like '🔴Live Sex🔴' to entice clicks on affiliate tracker URLs that pass a long user-identifying hash token ('userId=be19743d859c5f2c8f0f9a3a05f710f9d532baa09d175b73f0d16a28e90dea14'), enabling user tracking and profiling across redirect chains. (location: page.html:90-91)
hidden content
The page calls 'sendDataOnUnload()' on the 'beforeunload' event, suggesting data is exfiltrated when the user navigates away. The function is not defined in the visible HTML and must be loaded from an external script (main.js or similar), making its behavior opaque and unauditable from static analysis. (location: page.html:606-609)
curl https://api.brin.sh/domain/auntmia.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
auntmia.com currently scores 37/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.