Port 143 — IMAP
TCP well-known
What runs on port 143
Mail access that keeps messages on the server and syncs state across devices.
Security considerations
Unencrypted. Use port 993 for IMAP over TLS.
Checking whether something is listening
# Linux / macOS — what is bound to the port
sudo lsof -i :143
sudo ss -lntp | grep :143
# Windows
netstat -ano | findstr :143
Get-NetTCPConnection -LocalPort 143
# is it reachable from outside?
nc -zv example.com 143
curl -v telnet://example.com:143
Freeing the port
# find the process, then stop it
sudo lsof -ti :143 | xargs kill # Linux / macOS
netstat -ano | findstr :143 # note the PID, then:
taskkill /PID <pid> /F # Windows
Should this port be open to the internet?
Only on a mail server. If this port is open on something that is not intentionally handling mail, you may be running an open relay — which will get the IP blacklisted quickly.
Quick reference
| Port | 143 |
| Protocol | TCP |
| Service | IMAP |
| Range | Well-known (0–1023) — binding requires root on Unix |
Frequently asked questions
What is port 143 used for?
Mail access that keeps messages on the server and syncs state across devices.
Is it safe to open port 143?
Unencrypted. Use port 993 for IMAP over TLS.
How do I check if port 143 is open?
Locally, sudo lsof -i :143 on macOS or Linux, or netstat -ano | findstr :143 on Windows. From outside, nc -zv host 143 tells you whether anything answers.
Why do I get "address already in use" on port 143?
Another process is bound to it — often a previous run of your own program that did not exit cleanly. Find it with lsof -ti :143 and stop it, or configure your application to use a different port.
Can I change the port this service uses?
Almost always yes, in the service's configuration. Moving off a default port reduces automated scan noise, but it is obfuscation rather than security — a real attacker scans all 65,535.