Port 3507Nesh Broker

Nesh Broker service assigned to TCP and UDP port 3507.

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

Technical Details

what runs on :3507

Nesh Broker is registered on port :3507 over tcp and udp to Jeremy Maiden. 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 :3507

this machine

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

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

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

another host

nmap -sV -p T:3507 <host>
sudo nmap -sU -sV -p U:3507 <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 :3507

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 :3507 yet

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

Record

iana registry entry

port: :3507
service: Nesh Broker
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: Port 3507 is assigned to the Nesh Broker service by IANA. The assignment is registered to Jeremy Maiden; publicly documented deployment details are not available here.
lookups: 0rank 993
added: 2026-09-04
updated: 2026-09-04
references: IANA service name registry — port 3507

Something wrong?

This record is maintained by the engineers who use port 3507. 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-04.

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 :3507, by lookups.

port	service	proto	category	risk	views
:3483	Slim Devices Discovery	UDP	Streaming	caution	9.7k
:3483	SlimProto	TCP	Streaming	caution	9.0k
:3455	RSVP Protocol	TCPUDP	Network Services	caution	8.2k
:3516	Smartcard Service	TCPUDP	Security	caution	8.0k
:3544	Teredo	UDP	Security	caution	7.8k
:3527	MSMQ	UDP	Network Services	caution	7.3k
:3478	STUN	TCPUDP	Network Services	caution	7.0k
:3532	Raven RMC	TCPUDP	Remote Access	caution	5.9k

risk mix of the 8 listed

caution100%

0 of 8 encrypted

Port :3507Nesh Broker

Technical Details

Security Information

Related Ports

Port 3507Nesh Broker