About BDIX.app: Who We Are & Why You Can Trust Our Data

BDIX.app exists because one question kept costing Bangladeshi internet users hours: "does anyone actually know the current address for this server?" Forum posts from 2019, screenshots of screenshots, YouTube descriptions with dead IPs, Telegram groups selling free information - the local internet’s knowledge lived in places that rot. We built the reference that does not rot: a directory of BDIX servers, their addresses, their hosting ISPs, and their live status, alongside a directory of the ISPs themselves.

What This Site Is

• A server directory. Every major BDIX media server, its addresses and mirror nodes, its hosting ISP, and continuously-checked live status.
• An ISP directory. BTRC-licensed operators organised by tier and zone, with BDIX membership, coverage and package information where operators share it.
• Tools. BDIX tester, BDIX speed test, IP lookup, router login reference, USSD codes and the rest - the utilities the ecosystem kept rebuilding in comment sections.
• Guides. Evergreen, factual how-tos for using all of the above - the kind this blog publishes.

What This Site Is Not

• Not an ISP or operator. We are independent of every company we list - no ownership, no partnerships, no exceptions.
• Not a file host. We never host, mirror or link media files. We document the servers; what they carry and what they permit is between the operator and its users.
• Not a credential source. Server codes and portal logins live on the operators’ own pages, free. We point at them; we never republish them.
• Not BDIX itself. BDIX (the exchange) is a separate not-for-profit organisation; we cover the ecosystem around it and are unaffiliated with it.

How We Verify Data

Accuracy-first is the editorial rule, and in practice it means three things:

1. Named sources

Directory data comes from public registries - BTRC’s licence records, ISPAB membership, BDIX member lists - plus operator-published pages and our own monitoring. Where a page presents a fact, its source layer is identifiable. When we cannot verify something (an unconfirmed price, a rumoured address), the page says so instead of dressing the gap as fact.

2. Continuous monitoring

Every listed server is probed by our monitors, and directory pages show the latest result. This is the site’s founding feature: status is checked continuously by machines, not quoted from last month’s group post by humans.

3. Claim-and-correct

Operators claim their listings to correct or extend their data; readers report corrections through contact. Verified fixes go live fast. Unverified claims are labelled as claims - never silently promoted to fact. The verification policy documents the full process.

Editorial Standards

The guides on this blog follow the editorial policy in short:

• Factual, evergreen, useful. We write what stays true - how peering works, how to set up a portal - and avoid disposable news-chasing.
• Accuracy over completeness. A guide that admits uncertainty beats one that invents certainty. Where a fact changes often (codes, prices), we teach where the current value lives rather than quoting a value that expires.
• Safety-forward. The malware vector in this ecosystem is sideloaded "helper" apps and paid-code scams - not the protocol. Our guides say so, repeatedly, because it keeps being true.
• Independence. Listings, rankings and editorial are not for sale. The ranking methodology is published so it can be checked, and advertising never buys coverage.

How the Site Is Funded

Advertising - banner and in-content placements managed by us - and clearly-labelled outbound links. No paid listings, no sponsored posts inside guides, no affiliate deals that shape recommendations. If that economics ever changes, this section changes with it, in plain language.

Contact and Corrections

Found an error? Tell us - corrections from readers and operators are the cheapest quality mechanism there is. Operator? Claim your listing to keep your own data current. Bug in a tool? Same channel; the tools get fixed in public.