Port 80 — HTTP
An HTTP URL without an explicit port normally uses 80. The actual web-server configuration determines whether and where a listener exists.
Registry assignments, software defaults and local listeners are different things. A port number alone does not identify or secure a service.
Configuration and troubleshooting
For Nginx, inspect listen, server_name and the upstream target. Validate configuration syntax before reloading through your service manager.
Important limitations
Plain HTTP does not encrypt traffic. Use correctly configured HTTPS for credentials and sensitive data; an upstream may listen on a different port.
Read-only checks: run on the server host
Choose the commands for your OS. Check TCP and UDP separately. No result is not a lasting availability guarantee; inspect host and container separately.
Linux
sudo ss -ltnp 'sport = :80'macOS
sudo lsof -nP -iTCP:80 -sTCP:LISTENWindows PowerShell
Get-NetTCPConnection -LocalPort 80 -State ListenSources and review
Sources checked on:
This review covers the explanations and sources on this page, not your device or every community software entry below.
Related troubleshooting guides
Software Using This Port (5 software)
Community software entries: links are references, not individual verification.
Usage Suggestions
- Before using port 80, please confirm it is not occupied by other services
- If you encounter port conflicts, consider using other ports or stopping the occupying service
Quick Info
- Port
- 80
- Protocol
- TCP
- Categories
- Web & HTTP Services
- Usage Status
- 5 software in use
Related Ports
Need Help?
If you find incorrect information or need to add more, please submit correction information.
Submit Correction