Port 35Private Printer Server
Port 35 is unofficially associated with proprietary or private printer server protocols, typically for device discovery, configuration, and data exchange in local or enterprise printer networks. It can support both TCP and UDP transport modes, providing flexibility during printer communication setup and operation..
- transport
- tcp · udp
- in transit
- cleartext
- assignment
- unofficial
- risk
- 4/10
- lookups
- 12,540
2 transports registered
payload readable on path
used by convention
caution
rank 308 of 993 · top 31%
Technical Details
what runs on :35Port 35 is not officially assigned to any standardized protocol by IANA but has historically been utilized in some proprietary and private printer server implementations. It is often leveraged during initial printer discovery, network printer management, and print job negotiation in both peer-to-peer and client-server models. The bidirectional communication enabled on this port facilitates status reporting, configuration commands, and data transmission.
In many enterprise environments, printer servers supporting multiple devices use private or vendor-specific protocols for managing print queues, authenticating users, and spooling print jobs. The use of port 35 can be part of a closed ecosystem where printer management software communicates with printers over secure or insecure channels, depending on deployment.
TCP is typically used for reliable, connection-oriented sessions ensuring the integrity of print-related transactions, while UDP may be utilized for quick, connectionless discovery or simple status updates requiring low latency. Since port 35 is unofficial, adoption depends heavily on vendor implementations and legacy configurations.
Security Information
exposure of :35risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
network services averages 3.9 across 604 ports — this one sits 0.1 above.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
tcp · udp
udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite
security overview
Common Vulnerabilities:
- Unauthorized access if the printer server exposes sensitive management interfaces without authentication.
- Potential for information disclosure, such as network configurations or stored documents.
- Exploitation via poorly implemented protocols leading to denial of service or network congestion.
- Use as an entry point for lateral movement inside the network by attackers.
Common Mitigations:
- Segregating printer server networks from sensitive internal resources.
- Enforcing strong authentication and access controls on printer management interfaces.
- Disabling unused ports and protocols if not required.
- Keeping printer server firmware and software updated to patch known vulnerabilities.
- Monitoring printer-related traffic for anomalies and implementing firewall rules to restrict access to trusted hosts only.
Related Ports
the 8 most looked-up other ports in network services — 604 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :6543 | Jetnet | UDP | Network Services | caution | 65.3k |
| :5938 | TeamViewer | TCPUDP | Remote Access | caution | 65.0k |
| :8291 | Winbox MikroTik Admin | TCP | Security | caution | 62.9k |
| :3233 | WhiskerControl Protocol | TCPUDP | Network Services | caution | 61.9k |
| :3268 | Microsoft Global Catalog (GC) | TCPUDP | Security | caution | 54.6k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :3128 | Tatsoft Default HTTP Proxy | TCP | Web Services | caution | 46.8k |
risk mix of the 8 listed
- caution100%
0 of 8 encrypted