Port 3117MCTET Jserv

TCP/UDP 3117 is assigned to MCTET Jserv, registered by Portnoy Boxman; no protocol details are documented.

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

Technical Details

what runs on :3117

MCTET Jserv is registered on port :3117 over tcp and udp to Portnoy Boxman. 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 never observed open, so if it's open on your network it's more likely a custom or misconfigured service than the registered one.

find what's listening on :3117

this machine

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

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

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

another host

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

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

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

Record

iana registry entry

port: :3117
service: MCTET Jserv
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: The registry identifies the assignment as MCTET Jserv and lists Portnoy Boxman as the registrant. No established deployment or protocol behavior is known, and Nmap scan data has not observed it open.
lookups: 0rank 993
added: 2026-09-27
updated: 2026-09-27
references: IANA service name registry — port 3117

Something wrong?

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

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

port	service	proto	category	risk	views
:3128	Tatsoft Default HTTP Proxy	TCP	Web Services	caution	46.8k
:3128	Squid Proxy HTTP	TCP	Web Services	caution	45.8k
:3100	Tatsoft HTTP Port	TCP	Web Services	caution	19.4k
:3074	Xbox Live / Games for Windows	TCPUDP	Gaming	caution	10.9k
:3101	BlackBerry BES Cloud Comm	TCP	Cloud	caution	7.1k
:3054	AMT CNF PROT	TCPUDP	—	safe	0
:3094	Jiiva RapidMQ Registry	TCPUDP	Network Services	safe	0
:3170	SERVERVIEW-ASN	TCPUDP	—	safe	0

risk mix of the 8 listed

safe38%
caution63%

0 of 8 encrypted

Port :3117MCTET Jserv

Technical Details

Security Information

Related Ports

Port 3117MCTET Jserv