How We Verify BDIX Data

By BDIX Editorial · Sep 8, 2026 · Updated Sep 8, 2026

Every number on this site - every IP address, every server entry, every ISP record - comes from a documented process. This page is the exact methodology, so you can judge the data rather than take it on faith.

1. Reachability: Who Can Open a Server

We derive where each server is reachable from its node IPs:

Private IPs (like 10.16.100.244 or 172.16.x.x) mean the server sits on the hosting ISP's local network and is reachable only on that network.
Public IPs (like 103.58.73.6) mean the server is reachable across BDIX.

Because most servers cannot be probed from outside their reachability zone, we do not publish a fake up/down status. The server status tool runs live checks, and every directory row shows the reachability class instead of a guess.

2. IP Ownership: Mapping Addresses to ISPs

Each IP is mapped to its node and server, and to the ISP that operates it, using:

Public registration data (whois, ASN records) for public addresses.
BDIX and ISPAB member lists for operator identity.
Operator confirmations and the community BDIX server catalogue for private-address servers, which have no public registration.

Where ownership cannot be confirmed, the entry says so instead of guessing.

3. Changes: Real Dates, Real Records

When a server IP or node changes, we update the entry and record the real date of the change. New nodes, renumbered addresses and new servers are added as they are confirmed. We never invent or back-date these records - the editorial policy forbids fabricated freshness.

4. Weekly Verification Pass

Each week the directory is re-verified by hand: server pages are re-checked against the community catalogue, operator announcements and member lists, and stale entries are updated with the current date. This is why the directory's last-verified dates move, and why we trust them to mean something.

What We Will Not Verify

Live up/down of private-network servers - unverifiable from outside, so we do not fake it.
Content legality - we catalogue what servers host as information; we do not host, link to, or endorse downloads.
Speed or quality rankings of ISPs - the Top 50 list is an editorial ranking for BDIX access, not a measured performance test.

FAQ (Frequently Asked Questions)

How does BDIX verify its server data?

Every server entry is checked against the community BDIX server catalogue, public registration data such as whois and ASN records, BDIX and ISPAB member lists, and direct operator confirmations. Each page carries the real date it was last checked, and the whole directory gets a manual verification pass every week.

Why doesn't BDIX show whether a server is up or down right now?

Most BDIX servers sit on private addresses such as 10.16.100.244 or 172.16.x.x and are only reachable from the hosting ISP's own network, so a check from outside would always report "down". Instead of publishing a status we cannot verify, every directory row shows the reachability class - local network, BDIX peering or public - and the server status tool runs live checks from your own connection.

How does BDIX know which ISP operates an IP address?

Public addresses are mapped through whois and ASN registration records plus the BDIX and ISPAB member lists. Private-address servers have no public registration, so ownership comes from operator confirmations and the community server catalogue. Where ownership cannot be confirmed, the entry says so instead of guessing.

What does BDIX not verify?

Three things: live up/down state of private-network servers, whether the content a server hosts is licensed or legal, and measured ISP speed or performance. The Top 50 ISP list is an editorial ranking for BDIX access, not a benchmark of connection speed.