Port 1795 has no official assignment from IANA. No RFC. No registered service. But it wasn't always empty.
In the mid-2000s, EA Sports used port 1795 UDP for peer-to-peer online play in Madden NFL 2005, Madden NFL 2006, and Madden NFL 07 on PC. If you wanted to play Madden online during that era, you needed to forward this port on your router — a ritual as familiar then as it was frustrating.1
What Range Is This?
Port 1795 falls in the registered port range: 1024 through 49151.
This range sits between the well-known ports (0-1023), which are reserved for core Internet infrastructure and require IANA registration to use officially, and the ephemeral ports (49152-65535), which operating systems hand out temporarily for outgoing connections.
Registered ports are supposed to be formally claimed through IANA, but in practice many applications — especially games from the late 1990s and 2000s — simply picked numbers and used them without registering. Port 1795 is an example: EA used it, but it never appears in the official IANA registry with an assigned service name.2
What Ran Here
Madden NFL's PC multiplayer used a peer-to-peer model. When two players connected, their clients needed to communicate directly — which meant both sides needed open ports the other could reach.
UDP made sense for this. Unlike TCP, UDP doesn't establish a connection or guarantee delivery. For a football game where a dropped packet just means a slightly stuttered animation, the tradeoff was worth it. Low latency mattered. A missed acknowledgment did not.
The era of manually forwarding ports for games is largely over. Modern games use techniques like NAT traversal and STUN servers to punch through firewalls without user intervention. Port 1795's brief career as a gaming port belongs to the time when "check your port forwarding" was a standard troubleshooting step.
What's Listening on This Port Today
Almost certainly nothing — unless something on your specific machine is using it.
To check:
macOS / Linux:
Windows:
If those commands return nothing, the port is closed and idle. If something appears, the process ID will tell you what application claimed it.
Why Unassigned Ports Matter
The port space isn't infinitely large. 65,535 ports exist per protocol per IP address. The registered range covers most of them, and while IANA manages assignments, informal use is common — especially in software from before widespread awareness of the registry.
Unassigned ports matter for two reasons. First, they can be claimed by new services — what's unassigned today could be a registered protocol tomorrow. Second, they're frequently probed by scanners looking for services that might be listening without authorization. An unexpected process on port 1795 isn't inherently alarming, but it's worth understanding what it is.
Byla tato stránka užitečná?