BDIX Port Checker
Check whether a BDIX server port (21, 80, 8080, 443) is open and reachable from our probe host. For private BDIX IPs only. Tells you whether a server port answers before you troubleshoot FTP or HTTP.
Enter a private BDIX IP and a port. “Open” means something answered there within four seconds, “closed or filtered” means nothing did. The probe runs from our server, not from your device.
How This Port Checker Works
The tool opens a TCP connection from our probe host to the IP and port you enter, then reports whether it connects and how long the handshake took. Because the probe runs on our server, the result reflects reachability from inside the network. Your own ISP or router may still block the port even when ours reports it open.
Probing is limited to private BDIX ranges (10.x, 172.16–31.x, 192.168.x and carrier-grade NAT) so the tool stays a legitimate BDIX troubleshooting aid and cannot be abused as a public port scanner.
When to Check a Port
- When an FTP client cannot connect to a BDIX server and you want to test port 21.
- When a BDIX site will not load in a browser and you want to test port 80 or 443.
- When setting up a private server and verifying its port is reachable.
- When comparing reachability of two server IPs on the same port.
Common Ports and What They Mean
| Port | Normally used for | Test it when |
|---|---|---|
| 21 | FTP control connection | An FTP client or file manager will not connect. |
| 80 | HTTP web interface | A server web page will not load over plain HTTP. |
| 443 | HTTPS secure web interface | A server page will not load over HTTPS. |
| 8080 | Alternative HTTP / web admin console | A server panel or admin page runs on a non-standard port. |
| 990 | Implicit FTPS | A secure FTP client fails while plain FTP works. |
| 2121 | Alternative FTP port | FTP runs on a port other than 21. |
Start with the port your client is actually trying to use. Most BDIX media servers answer on 21 for file access and 80 or 8080 for their web door, so those are the four worth testing first.
How to Read the Result
- Open: the port completed a TCP handshake from our probe host. Something is listening there. The latency shown is how long the handshake took.
- Closed or filtered: nothing answered within four seconds. The server may be down, the service may not be running, or a firewall may be dropping the packets.
- A closed result here but a working server on your own connection usually means your ISP or router filters that port, or the server only accepts connections from its own hosting ISP.
- A fast handshake time means the path is short and healthy. Tens of milliseconds is normal for a BDIX host; hundreds of milliseconds suggests the traffic is leaving the local network.
One probe is a snapshot, not a diagnosis. If a port matters, test it twice a few minutes apart before concluding the server is down.
FAQ (Frequently Asked Questions)
What Does Closed / Filtered Mean?
The port did not respond within 4 seconds from our probe host. The server may be down, the port may be blocked by a firewall, or your ISP may not route that port.
Why Can I Only Test Private IPs?
This tool is designed for BDIX servers, which live in private IP ranges. Restricting probes to private ranges keeps the tool from being misused as a public port scanner.
What Ports Should I Test for BDIX Servers?
FTP usually listens on 21, web interfaces on 80 or 8080, and secure sites on 443. Start with the port your client or browser is trying to use.
A Port Is Open Here but Not for Me: Why?
The probe runs from our server inside the network. Your ISP or router may filter that port, or the server may only allow the hosting ISP own range. The result is a hint, not a guarantee for your connection.