context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
Clickunder ad script dynamically loads external JavaScript from 'ftd.agency' CDN via an obfuscated self-executing function. The script fires once every 24 hours using localStorage tracking, silently appending a div and loading a remote script that can redirect users to arbitrary destinations without their consent. This is a well-known clickunder/popunder ad network technique used to hijack user navigation. (location: page.html:49-84, page-text.txt:4-37)
malicious redirect
Affiliate ad link uses a tracking redirect domain 'refpa35840.pro' with tag/site/ad parameters, redirecting through an affiliate network before reaching the advertised destination. The intermediate domain obscures the final landing page and could route users through malicious or deceptive ad networks. (location: page.html:206)
malicious redirect
Affiliate ad link uses 'mlbt.cc' short URL redirect (labeled 'MELBET') which obscures the final destination. Short/redirect URLs used in ad placements can route users to gambling affiliate pages or phishing sites without transparent disclosure of the destination. (location: page.html:1117)
social engineering
The site aggressively promotes a paid 'Investment Plan' with language like 'Guarantee your Return on Investment', '95% success rate', and 'Guaranteed daily profits'. This is classic social engineering targeting financially motivated users — presenting gambling tips as a reliable investment vehicle, which is deceptive and exploits loss-aversion psychology to solicit payment for VIP/premium tip subscriptions. (location: page.html:1144-1147, page-text.txt:1098-1101)
social engineering
Repeated unverifiable superlative claims throughout page copy ('90% accuracy or higher', '97.4% successful code conversions', '3,700+ matches analyzed') presented as factual metrics without third-party verification, designed to build false trust and encourage users to subscribe to paid VIP tips or place bets based on fabricated credibility statistics. (location: page.html:1785-1826, page-text.txt:1742-1781)
hidden content
A Cloudflare challenge-platform iframe is injected dynamically via an immediately-invoked function expression (IIFE). The iframe is styled with height=1, width=1, position absolute, visibility hidden — rendering it completely invisible to users. While Cloudflare bot-detection is a known use case, this pattern of hidden iframe injection can also be used to load hidden content, perform covert tracking, or fingerprint visitors. (location: page.html:2020, page-text.txt:1974)
obfuscated code
The clickunder ad loader uses an obfuscated IIFE pattern with single-letter variable names (w,d,o,g,r,a,m), dynamic script source construction via string concatenation ('https://cdn.'+w[r+'h']+'/libs/e.js'), and a fallback domain array (['ftd.agency']). This obfuscation pattern is typical of malvertising payloads designed to evade static analysis and content security scanning. (location: page.html:64-78)
social engineering
Keywords meta tag includes phrases like 'fixed matches prediction', '100% winning tips', and 'guaranteed football tips' — terms associated with match-fixing fraud and impossible guarantees used to lure vulnerable gamblers. While this is in metadata and not directly shown to users, it signals intentional targeting of users searching for fraudulent match-fixing services. (location: page.html:21)
curl https://api.brin.sh/domain/acepredict.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
acepredict.com currently scores 40/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.