Is directpredict.com safe?

suspiciouslow confidence
41/100

context safety score

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

identity
90
behavior
80
content
1
graph
71

9 threat patterns detected

high

phishing

5 deceptive links where visible host does not match destination host

high

social engineering

Site makes repeated unverifiable claims of '100% sure' and '100% winning assurance' football predictions, exploiting gambling psychology to induce users to pay for VIP subscription packages. Claims of '95%+ accuracy' and 'average accuracy above 95%' are unsubstantiated marketing designed to manipulate bettors into financial decisions. (location: page.html:418, page.html:2514, page.html:2529, page.html:2543)

medium

malicious redirect

Third-party ad network script from 'traffmovie.com' is dynamically loaded via an obfuscated self-invoking function using a domain array fallback pattern. The script constructs a CDN URL at runtime ('https://cdn.' + domain + '/libs/e.js'), which can serve arbitrary JavaScript and redirect users without their knowledge. Two separate ad zones are loaded this way (zone_1156046037 and zone_1272257534). (location: page.html:166-176, page.html:292-302)

low

malicious redirect

A JavaScript click handler intercepts all document click events and redirects the browser via window.location.href based on a data-link attribute. While used here for tab navigation, this pattern can be abused to redirect users to off-domain URLs without the normal anchor-tag transparency. (location: page.html:3029-3035)

medium

hidden content

Multiple anchor links with class 'd-none' (CSS display:none) are present in the page body. These hidden links point to internal betting odds pages (/2-odds, /sure-3-odds-banker, /5-odds, /10-odds, /20-odds, /100-odds, /direct-win-prediction) and appear designed for SEO manipulation rather than user navigation, constituting hidden link spam. (location: page.html:2608-2616)

medium

social engineering

Navigation menu contains a vague dropdown item labeled 'Text link 1' linking to the external domain nicepredict.com with anchor text 'Sure Winning Tips'. The deliberately generic label conceals the true destination and purpose of the link, a deceptive UI pattern used to funnel users to affiliate sites. (location: page.html:355-364)

medium

social engineering

Footer contains an extensive list of off-domain outbound links styled to appear as neutral 'partner' references, including links to domains such as blackbroadwaywashingtondc.com labeled as '1xbet giriş' (a gambling brand login page in Turkish), stakevilla.com, forebetpredict.com/raja-win678, and others. These links blend legitimate-looking sports resources with potentially unvetted or fraudulent gambling destinations. (location: page.html:2732-2899)

low

social engineering

The page promotes a paid 'Investment Scheme' framed as a financial opportunity with a tracker showing historical win/loss results to create false confidence. The 'Investment Result' section selectively displays wins to manufacture social proof for a gambling subscription product, constituting deceptive financial solicitation. (location: page.html:2082-2201)

low

hidden content

The JSON-LD structured data schema identifies the site organization name as 'Laravel' (the PHP framework) rather than the actual business name, which is a metadata inconsistency suggesting autogenerated or misconfigured schema markup that could mislead crawlers and AI agents parsing the page's semantic data. (location: page.html:133-145)

API

curl https://api.brin.sh/domain/directpredict.com

FAQ: how to interpret this assessment

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

Is directpredict.com safe for AI agents to use?

directpredict.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.

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 25, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Trust Graph

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.