Port 503 is officially assigned to "Intrinsa" in the IANA registry. In practice, you'll almost never encounter Intrinsa traffic on this port. Instead, port 503 has become the de facto alternative port for Modbus TCP communications and the home of MCode/TCP, a protocol for controlling MDrive motor controllers.
This is the Internet's way of repurposing real estate. Official assignment says one thing. Actual usage says another.
What Actually Uses Port 503
MCode/TCP: When you connect to an MDrive motor controller on port 503, it automatically enters MCode/TCP mode—a protocol based on one and two-character mnemonics from the MDrive programming language. The controller becomes fully programmable, operating identically to its RS-422/485 counterparts but over TCP/IP.1
Alternative Modbus TCP Port: While Modbus TCP officially lives on port 502, many industrial setups run multiple Modbus servers on the same device. Port 503 (and 504, and beyond) serves as the overflow. You can run Modbus TCP on port 502 and Modbus RTU over TCP on port 503 with no conflict.23
The ability to use different ports depends on whether both your device and polling driver allow port configuration. Most modern industrial equipment does.
The Official Assignment: Intrinsa
The IANA registry lists port 503 as assigned to "Intrinsa" for both TCP and UDP.4 Some sources describe Intrinsa as "a secure communication channel for transmitting and managing data from medical devices,"5 but documentation is scarce and actual implementations are essentially nonexistent in the wild.
There was an Intrinsa Corporation—a software testing company acquired by Microsoft in 19996—but no evidence connects it to this port assignment. The medical device description appears in port databases without primary sources.
What's clear: whatever Intrinsa was supposed to be, it didn't take hold. The port sat mostly empty until industrial automation found a use for it.
Well-Known Ports and Assignment
Port 503 falls in the well-known ports range (0-1023), also called System Ports. These ports require IETF Review or IESG Approval for assignment—a more stringent process than for higher port numbers.7
The fact that port 503 received an official assignment but is now primarily used for something else entirely shows the tension between centralized planning and organic network evolution. IANA assigns. The Internet uses. Sometimes those align. Sometimes they don't.
Security Considerations
If you're running Modbus TCP on port 503, understand that Modbus has no built-in authentication or encryption. Every command is sent in the clear. Anyone who can reach the port can read the traffic and potentially send commands to your industrial equipment.
Modbus was designed in 1979 for factory floor networks that were physically isolated. Running it over TCP/IP without additional security layers (VPNs, network segmentation, authentication proxies) exposes your industrial control systems to the Internet.
Port 503 doesn't make Modbus more or less secure than port 502. The protocol's limitations remain the same regardless of which door it uses.
Checking What's Listening on Port 503
On Linux, use netstat to see if anything is listening:
Or use lsof to check specifically for port 503:
Both commands will show you the process name, PID, and protocol (TCP or UDP) if something is bound to the port.8
Related Ports
Port 502: The official Modbus TCP port. If you're using port 503 for Modbus, you're probably using 502 as well.
Port 504+: Additional overflow ports for multi-server Modbus configurations.
Why This Port Matters
Port 503 is a case study in how the Internet actually works versus how it's supposed to work. Somewhere, someone registered "Intrinsa" and got IANA approval. The service never materialized or failed to gain adoption.
Meanwhile, factory automation engineers needed a way to run multiple Modbus servers on the same device. They looked at port 502, looked at port 503 sitting right next door, and thought "that'll work."
No RFC. No formal specification. Just practical necessity meeting available infrastructure.
The Modbus traffic flowing through port 503 right now—in factories, in building automation systems, in industrial control networks—doesn't know or care what the port was originally assigned for. It just works.
That's the Internet. A registry says one thing. The packets say another. The packets usually win.
Frequently Asked Questions
Was this page helpful?