Firebind

Firebind


Based on Java technology, Firebind enables a user to test any TCP or UDP port(s) in the outbound direction to determine whether they are being blocked by a firewall. Internet users can encounter blocked ports on a regular basis, whether it's their own client firewall (such as Windows Firewall), a home or enterprise router/firewall, or their ISP's firewall doing the blocking.

By using a client/server architecture, the Firebind Server can listen on any of the 65535 TCP or UDP ports. The client then sends unique data to the chosen port that the server is listening on. The server then returns the data, and if it arrives back at the client unchanged, the port is not blocked.

If a port is blocked, Firebind can categorize each port failure into one of the following types of error cases:

Passed
Handshake Connection Initiation Failure
Handshake Connection Refused
Handshake Connection Timed Out
Handshake Connection Completion Failure
Payload Send Failure
Payload Receive Time Out
Payload Receive Refused
Payload Receive Mismatch
Payload Receive Error

Firebind is useful for many types of end users, including:

- IT Administrators who would like to validate their outbound corporate firewall rules or who need a tool to help their mobile users validate Internet connectivity
- Home users trying to troubleshoot application connectivity to the Internet
- Traveling users on public wired broadband or WiFi who may be subject to very restrictive Internet access

Before Firebind, users could try to telnet to the port in question, but the results weren't conclusive and that trick was only useful (if at all) for TCP. Tools like yougetsignal.com, canyouseeme.org, and grc.com are meant to test inbound connections (from Internet to client machine), usually to validate whether a user has set up their port forwarding rules in their firewall correctly. Other tools like NMAP are port scanners which are designed to probe for open ports on a target machine using a specific IP address. A port scanner is only useful to test a single IP address for vulnerabilities and doesn't help a user determine whether their path to the Internet is being blocked.

Firebind is a "Path Scanner". With Firebind, any Internet user can now test for firewall blocking that until now only networking experts could determine, if at all.

Firebind - if you can't connect, you can't communicate...

Recent changes:
Enhanced handling of failed UDP ports. Updated for latest Android SDK.
Add to list
Free
76
3.8
User ratings
93
Installs
10,000+
Concerns
0
File size
146 kb
Screenshots
Screenshot of Firebind Screenshot of Firebind Screenshot of Firebind

About Firebind
Based on Java technology, Firebind enables a user to test any TCP or UDP port(s) in the outbound direction to determine whether they are being blocked by a firewall. Internet users can encounter blocked ports on a regular basis, whether it's their own client firewall (such as Windows Firewall), a home or enterprise router/firewall, or their ISP's firewall doing the blocking.

By using a client/server architecture, the Firebind Server can listen on any of the 65535 TCP or UDP ports. The client then sends unique data to the chosen port that the server is listening on. The server then returns the data, and if it arrives back at the client unchanged, the port is not blocked.

If a port is blocked, Firebind can categorize each port failure into one of the following types of error cases:

Passed
Handshake Connection Initiation Failure
Handshake Connection Refused
Handshake Connection Timed Out
Handshake Connection Completion Failure
Payload Send Failure
Payload Receive Time Out
Payload Receive Refused
Payload Receive Mismatch
Payload Receive Error

Firebind is useful for many types of end users, including:

- IT Administrators who would like to validate their outbound corporate firewall rules or who need a tool to help their mobile users validate Internet connectivity
- Home users trying to troubleshoot application connectivity to the Internet
- Traveling users on public wired broadband or WiFi who may be subject to very restrictive Internet access

Before Firebind, users could try to telnet to the port in question, but the results weren't conclusive and that trick was only useful (if at all) for TCP. Tools like yougetsignal.com, canyouseeme.org, and grc.com are meant to test inbound connections (from Internet to client machine), usually to validate whether a user has set up their port forwarding rules in their firewall correctly. Other tools like NMAP are port scanners which are designed to probe for open ports on a target machine using a specific IP address. A port scanner is only useful to test a single IP address for vulnerabilities and doesn't help a user determine whether their path to the Internet is being blocked.

Firebind is a "Path Scanner". With Firebind, any Internet user can now test for firewall blocking that until now only networking experts could determine, if at all.

Firebind - if you can't connect, you can't communicate...

Recent changes:
Enhanced handling of failed UDP ports. Updated for latest Android SDK.

Visit Website
User reviews of Firebind
Excellent!!!
Mar 16, 2011
Android Market Comments
A Google User
Jun 15, 2014
Cool
A Google User
May 23, 2014
This app is dead. The server doesn't exist. I wrote a note to Google to remove it. No answer yet Don't waste your time/bandwidth. Great idea if the server it's looking for still existed
A Google User
Apr 28, 2014
Failed?
A Google User
Apr 3, 2014
Used to be great. It's dead now. Seems their servers have been sunset'd with no warning or explanation.
A Google User
Feb 10, 2014
Network Error Unable to contact Firebind service.