Port 720Simple Message Queue Protocol
The Simple Message Queue Protocol (SMQP) is a lightweight messaging protocol used to enable communication between distributed systems through queuing mechanisms. It facilitates asynchronous message delivery, allowing different applications and services to exchange data efficiently without requiring direct synchronous connections..
- transport
- tcp
- in transit
- cleartext
- assignment
- unofficial
- risk
- 4/10
- lookups
- 5,998
single transport
payload readable on path
used by convention
caution
rank 829 of 993 · top 83%
Technical Details
what runs on :720SMQP is designed to provide a minimalistic, efficient method for message-oriented communication between distributed components. It abstracts the complexity of underlying network communication and allows applications to enqueue messages that can be processed asynchronously. This design is particularly beneficial for decoupling application components and facilitating scalable architectures.
The protocol supports fundamental operations such as enqueueing, dequeueing, acknowledgment, and error handling. Clients submit messages to queues, which can then be processed by consumers at their convenience. This pattern improves reliability, as messages persist until successfully handled, and can aid in implementing load balancing and failover mechanisms.
SMQP typically operates over TCP to ensure reliable, ordered delivery of messages. Implementations may vary since SMQP is not an officially standardized IETF protocol, but it follows core messaging concepts similar to other queuing protocols like AMQP or MQTT, albeit in a simpler, more lightweight fashion.
Security Information
exposure of :720risk 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
every listening transport is another surface to filter at the edge
security overview
Common Vulnerabilities:
- Lack of strong authentication may lead to unauthorized access to queues.
- Absence of data encryption can cause message interception and eavesdropping.
- Susceptibility to denial-of-service (DoS) attacks through flood of bogus messages.
- Improper input validation can expose the system to injection attacks.
Common Mitigations:
- Implement network segmentation and firewall rules to restrict access.
- Use secure tunnels (e.g., VPN, SSH) or transport layer protocols such as TLS to encrypt message flows.
- Employ strong authentication and authorization mechanisms for clients.
- Monitor queue activity and apply rate limiting to detect and mitigate DoS patterns.
- Sanitize inputs and validate message contents to prevent injection and malformed data attacks.
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