context safety score
A score of 41/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
malicious redirect
Post click handler opens two simultaneous navigations on every click: window.open(postItem.dataset.there, '_blank') opens a new tab and window.location = postItem.dataset.here navigates the current tab. This dual-navigation pattern is a well-known technique used by adult traffic brokers to fire affiliate/ad redirect chains without user consent, sending traffic to potentially harmful third-party destinations. (location: page.html:503-510)
hidden content
Yandex Metrika tracking pixel is hidden off-screen via inline style 'position:absolute; left:-9999px;' to silently track all visitors including link clicks (trackLinks:true), webvisor session recording (webvisor:true), and ecommerce dataLayer events — collecting behavioral data covertly. (location: page.html:606)
hidden content
The .ad-container CSS class is set to 'display:none', hiding ad containers from direct view while still loading and executing ad network scripts (magsrv.com, twinrdengine.com). This conceals the full scope of third-party ad code being run on the page. (location: page.html:14-16)
social engineering
Age verification modal (class 'age-verification') with z-index:9999 is defined in CSS and styled to overlay the full page, designed to gate adult content behind a trivially bypassable yes/no confirmation with no real verification — a dark pattern that collects implicit consent and may be used to justify downstream data use or ad targeting. (location: page.html:102-127)
malicious redirect
Third-party ad script loaded from twinrdengine.com (https://s.ad.twinrdengine.com/adlib.js) — an ad network associated with aggressive redirects and pop-under advertising. Combined with the dual-navigation click handler, users can be silently redirected to malvertising chains. (location: page.html:610)
hidden content
Yandex Metrika is initialized with webvisor:true, enabling full session replay (mouse movements, clicks, keystrokes) on all visitors — a significant privacy/surveillance mechanism that operates without explicit user disclosure on the page. (location: page.html:604)
social engineering
The site uses clickid and source URL parameters to track affiliate referral chains (page.html:483-488), appending them silently to all internal navigation links. This is standard affiliate fraud/tracking infrastructure used to monetize user traffic through undisclosed third-party relationships. (location: page.html:483-510)
curl https://api.brin.sh/domain/feedtofap.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
feedtofap.com currently scores 41/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.