Port 24554Binkp Fidonet Mail
**Binkp** is a protocol designed to facilitate the exchange of Fidonet mail packets over TCP/IP networks, utilizing port 24554. Originally developed to modernize the transfer of echomail and netmail across Fidonet nodes, Binkp allows traditional store-and-forward bulletin board systems to communicate reliably over the Internet, rather than legacy dial-up methods..
- transport
- tcp · udp
- in transit
- cleartext
- assignment
- official
- risk
- 4/10
- lookups
- 5,825
2 transports registered
payload readable on path
registered with iana
caution
rank 846 of 993 · top 85%
Technical Details
what runs on :24554Introduction
Binkp (Binary Internet Kit Protocol) is a specialized protocol enabling Fidonet-compatible mailers and bulletin board systems (BBS) to transfer messages and files over modern TCP/IP networks. Fidonet is an old but still operational global network for BBSs, traditionally reliant on dial-up. Binkp modernizes this by replacing modem-based connections with more reliable and faster Internet-based communication.
Protocol Design
Operating primarily over port 24554, Binkp uses a simple binary-based protocol to negotiate sessions, authenticate peers, and transfer mail bundles. Both TCP and UDP modes can be available, but TCP is most commonly employed due to its reliability in packet delivery. Binkp supports error checking, compression, and multi-packet transfer routines that efficiently handle large mail bundles.
Deployment Scenarios
Today's implementations use Binkp as the backbone for links among Fidonet nodes spread worldwide. This allows hobbyists, retro communities, and certain small-scale networks to maintain communication without traditional phone lines. Clients typically run as dedicated mailers integrated within BBS software or standalone mailer packages.
Security Information
exposure of :24554risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
email averages 3.9 across 42 ports — this one sits 0.1 above.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
official
registered with iana for this service — scanners fingerprint it by number
reachable over
tcp · udp
udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite
security overview
Common Vulnerabilities:
- Lack of encryption: Since Binkp's original protocol does not mandate encryption, message content and authentication details could be intercepted by attackers.
- Weak authentication: Some Binkp implementations use simple password-based schemes vulnerable to brute-force or replay attacks.
- Open port exposure: Running Binkp with publicly accessible ports can allow attackers to attempt unauthorized connections or conduct denial-of-service attacks.
Common Mitigations:
- Utilize tunneling such as VPNs or SSH port forwarding to encrypt the data in transit.
- Configure strong, complex link passwords and limit allowed peers to known systems.
- Restrict network exposure by using firewalls and IP whitelisting.
- Keep software updated to minimize bugs or vulnerabilities present in outdated implementations.
Related Ports
the 8 most looked-up other ports in email — 42 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :143 | IMAP | TCPUDP | caution | 20.7k | |
| :995 | POP3S | TCPtls | caution | 18.8k | |
| :109 | POP2 | TCP | caution | 17.9k | |
| :2096 | cPanel SSL Webmail | TCPtls | Web Services | safe | 17.4k |
| :110 | POP3 | TCP | caution | 15.5k | |
| :993 | IMAPS | TCPtls | caution | 14.5k | |
| :1352 | Lotus Notes RPC | TCP | caution | 12.3k | |
| :24 | Private Mail | TCPUDP | caution | 11.7k |
risk mix of the 8 listed
- safe13%
- caution88%
3 of 8 encrypted