context safety score
A score of 44/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
Two third-party scripts loaded from bundleinhabit.com, an unknown domain with no legitimate reputation. The first script uses a highly obfuscated, randomized path (/gFRzv9M/U9x4Ernitvn7Z69q/6_XHFfUB/hqyg4YgF/x-cAKzKf5e7E/cgyRRBFZWqzUZaiFJAJ/OFNVdGJfKk/sexP/euT/9e0b6hVdFxH/bFD8Q4LlCCtlhk/FXCeFIFU/iD5Bh) characteristic of malvertising, ad-fraud, or malware delivery networks. The second uses a hash-based JS filename. Both are loaded in the main page HTML. (location: page.html - <script src='//bundleinhabit.com/...'> (two instances))
hidden content
A <details> HTML element uses a full Telegram invite URL (https://t.me/+8VQ8dSB70zszOTk1) as its HTML id attribute. This is a structural misuse of the id attribute — valid HTML ids must not be URLs — and may serve to embed a channel redirect link in a way that is invisible to casual inspection but parseable by scrapers or AI agents reading the DOM. (location: page.html - <details id="https://t.me/+8VQ8dSB70zszOTk1">)
malicious redirect
A 'View All' button in the page links to https://localhost/gpf5yt/category/news/ — a localhost URL that has no meaning in a production context. This is either a leaked development artifact that could redirect users to a local server (exploitable in some network configurations) or a placeholder for a future redirect swap. (location: page.html - <a class="gb-button gb-button-eae17b94" href="https://localhost/gpf5yt/category/news/">)
hidden content
The document.referrer property is overridden at page load via sessionStorage manipulation (litespeed_docref pattern). While marketed as a LiteSpeed Cache feature, this technique spoofs the HTTP referrer visible to page scripts, which can be used to bypass referrer-based analytics, security checks, or deceive monitoring tools about traffic origin. (location: page.html - inline script at start of <head>: var litespeed_docref=sessionStorage.getItem("litespeed_docref")...Object.defineProperty(document,"referrer",...))
social engineering
The site prominently features multiple articles promising easy money via bKash (Bangladeshi mobile banking): 'ভিডিও দেখে টাকা ইনকাম' (earn by watching videos), 'বিকাশে ৫০ টাকা বোনাস অফার' (bKash 50 taka bonus offer), and 'অনলাইনে আয় বিকাশে পেমেন্ট' (online income via bKash). These are classic lure articles used to drive traffic from users seeking quick income, potentially funneling them to affiliate scams or credential-harvesting pages. (location: page.html / page-text.txt - homepage article listings and internal links to /collect-bkash-50-taka-bonus/ and /online-income-bkash/)
curl https://api.brin.sh/domain/tipsnetbd.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
tipsnetbd.com currently scores 44/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.