Port 6677Unassigned Port
Port 6677 has no registered IANA service assignment.
- transport
- unknown
- in transit
- cleartext
- assignment
- unofficial
- risk
- 0/10
- lookups
- 0
single transport
payload readable on path
used by convention
safe
rank 993 of 6,689 · top 15%
Technical Details
what runs on :6677There is no registered protocol for port 6677, so it has no standard transport, handshake, framing, or related-port convention. Any observed TCP, UDP, or SCTP traffic on this port should be identified from the application or host configuration that generated it.
Security Information
exposure of :6677risk score
0/ 10safe
routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.
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
unknown
every listening transport is another surface to filter at the edge
security overview
The port number alone does not identify a service or its security properties. If traffic is observed, identify the listening process and its configuration; do not assume it is safe to expose merely because the port is unassigned.
Related Ports
ports registered around :6677, by lookups.
| port | service | risk | |||
|---|---|---|---|---|---|
| :6697 | IRC over SSL | TCPtls | Security | caution | 16.4k |
| :6619 | Odette FTPS | TCPUDPtls | Security | caution | 16.0k |
| :6646 | McAfee Agent Discovery | UDP | Security | caution | 15.8k |
| :6679 | IRC SSL | TCPtls | Security | caution | 15.7k |
| :6665 | IRC | TCP | Network Services | caution | 10.5k |
| :6660 | IRC | TCP | Voice and Chat | caution | 10.2k |
| :6699 | WinMX | TCP | File Transfer | caution | 4.5k |
| :6627 | Allied Electronics NeXGen | TCPUDP | — | safe | 0 |
risk mix of the 8 listed
- safe13%
- caution88%
3 of 8 encrypted