Port 107Remote Telnet
Port 107 is traditionally associated with the Remote Telnet service, providing remote login and command-line access to servers and network devices over plaintext connections. While Telnet was once widely used for managing networked systems, it has largely been replaced by more secure protocols such as SSH due to its lack of encryption, which poses a significant security risk when transmitting credentials and data. Nonetheless, some legacy systems or network devices may still use this port for diagnostic or management purposes in controlled environments..
- transport
- tcp
- in transit
- cleartext
- assignment
- official
- risk
- 4/10
- lookups
- 8,044
single transport
payload readable on path
registered with iana
caution
rank 631 of 993 · top 64%
Technical Details
what runs on :107Port 107 was officially assigned for the Remote Telnet Service, which is an extension or an alternative port for standard Telnet traffic that typically occurs on port 23. Telnet provides a bidirectional interactive text-oriented communication facility using a virtual terminal connection over the TCP/IP protocol. It allows users to remotely connect and manage systems via a command-line interface.
Unlike SSH, Telnet transmits data, including usernames and passwords, in plaintext, which makes it easy to intercept communications using packet sniffers. Port 107 historically served situations where a secondary Telnet service was needed, such as for segregated management access or specific network functions distinct from the primary Telnet service.
In contemporary networking, Telnet's primary port remains 23, and use of port 107 is rare and typically limited to legacy equipment or specialized environments. Modern best practices recommend using encrypted alternatives due to inherent security concerns with plaintext protocols.
Security Information
exposure of :107risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
remote access averages 4.0 across 110 ports — this one sits level with it.
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
every listening transport is another surface to filter at the edge
security overview
Common Vulnerabilities
- Transmission of credentials in plaintext, making them susceptible to interception and replay attacks
- Susceptibility to man-in-the-middle (MITM) attacks due to lack of encryption and authentication
- Potential exploitation for unauthorized remote system access if authentication is weak or misconfigured
- Exposure to brute-force attacks targeting login credentials
Common Mitigations
- Replace Telnet services with secure alternatives like SSH, which provide encrypted communications
- If Telnet must be used, restrict access through firewall rules, network segmentation, and allowed host lists
- Enforce strong authentication mechanisms and complex passwords
- Monitor network traffic for unauthorized Telnet usage
- Disable unused Telnet services and remove legacy support when possible
- Employ intrusion detection and prevention systems to detect suspicious activity on port 107
Related Ports
the 8 most looked-up other ports in remote access — 110 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :8000 | Intel Remote Desktop / Alternate HTTP Port | TCP | Web Services | safe | 84.3k |
| :8888 | D2GS Admin Console | TCP | Remote Access | caution | 83.7k |
| :8881 | Atlasz Secure Server | TCP | Web Services | caution | 67.6k |
| :5938 | TeamViewer | TCPUDP | Remote Access | caution | 65.0k |
| :8291 | Winbox MikroTik Admin | TCP | Security | caution | 62.9k |
| :8008 | IBM HTTP Server Admin | TCP | Web Services | caution | 58.3k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :23 | Telnet | TCP | Remote Access | caution | 34.8k |
risk mix of the 8 listed
- safe13%
- caution88%
0 of 8 encrypted