Port 6850ICCRUSHMORE

An IANA-assigned ICCRUSHMORE service registered to Dave Hubbard; public protocol details are unavailable.

transport: tcp · udp
in transit: cleartext
assignment: official
risk: 1/10
lookups: 0

Technical Details

what runs on :6850

ICCRUSHMORE is registered on port :6850 over tcp and udp to Dave Hubbard. We don't have a technical write-up for it beyond the IANA registry entry.

In nmap's internet-wide scan data this port is found open rarely. What's listening is often not the registered service, so check before you assume.

find what's listening on :6850

this machine

# linux
sudo ss -tulpn 'sport = :6850'

# macos / bsd
sudo lsof -nP -i :6850

# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :6850

another host

nmap -sV -p T:6850 <host>
sudo nmap -sU -sV -p U:6850 <host>

run it? the handshake, the implementations you meet in the wild and the flags that matter come from the engineers who do.

add technical details

Security Information

exposure of :6850

risk score

1/ 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

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

no security notes recorded for :6850 yet

known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.

Record

iana registry entry

port: :6850
service: ICCRUSHMORE
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: Ports 6850/tcp and 6850/udp are assigned to the ICCRUSHMORE service. The assignment is registered to Dave Hubbard, but the registry provides no protocol or product information.
lookups: 0rank 993
added: 2026-09-07
updated: 2026-09-07
references: IANA service name registry — port 6850

Something wrong?

This record is maintained by the engineers who use port 6850. Every field on it is editable — change what's wrong, say how you know, and a reviewer publishes it, usually within a minute. Last touched 2026-09-07.

01edit any field on a page of its own
02a model checks it for accuracy and spam
03clean and confident goes live immediately

edit this record →back to the registry

Related Ports

browse categories →

ports registered around :6850, by lookups.

port	service	proto	category	risk	views
:6888	BitTorrent	TCPUDP	File Transfer	caution	13.4k
:6889	BitTorrent	TCPUDP	File Transfer	caution	11.2k
:6888	MUSE	TCPUDP	File Transfer	caution	11.2k
:6881	BitTorrent	TCPUDP	File Transfer	caution	10.9k
:6901	BitTorrent	TCPUDP	File Transfer	caution	10.2k
:6891	BitTorrent Data Transfer	TCPUDP	File Transfer	caution	9.9k
:6902	BitTorrent	TCPUDP	File Transfer	caution	9.7k
:6789	LoggerNet Datalogger	TCP	Network Services	caution	9.2k

risk mix of the 8 listed

caution100%

0 of 8 encrypted

Port :6850ICCRUSHMORE

Technical Details

Security Information

Related Ports

Port 6850ICCRUSHMORE