Port 8768Sandpolis Server

TCP port 8768 is assigned to Sandpolis Server, a service registered by Tyler Cook.

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

1 other service is registered on port 8768. compare all 2 →

Technical Details

what runs on :8768

Sandpolis Server is registered on port :8768 over tcp to Tyler Cook, assigned November 2019. 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 :8768

this machine

# linux
sudo ss -tlpn 'sport = :8768'

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

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

another host

nmap -sV -p T:8768 <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 :8768

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

every listening transport is another surface to filter at the edge

security overview

no security notes recorded for :8768 yet

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

Record

iana registry entry

port: :8768
service: Sandpolis Server
transport: TCP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: IANA assigns TCP 8768 to Sandpolis Server, registered by Tyler Cook in 2019. I don't have reliable details on deployments or protocol behavior beyond that assignment.
lookups: 0rank 993
added: 2026-10-14
updated: 2026-10-14
references: IANA service name registry — port 8768

Something wrong?

This record is maintained by the engineers who use port 8768. 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-10-14.

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

port	service	proto	category	risk	views
:8767	TeamSpeak	UDP	Network Services	caution	5.7k
:8768	TeamSpeak Alt	UDP	Gaming	caution	5.5k
:8802	Unassigned Port		—	safe	0
:8766	Agilent Connectivity Service	TCPUDP	System	safe	0
:8786	Message Client	TCPUDP	Network Services	safe	0
:8778	Stonebranch Universal Enterprise Controller	TCP	—	safe	0
:8765	Ultraseek HTTP	TCPUDP	Web Services	safe	0
:8800	Sun Web Server Admin Service	TCPUDP	Web Services	safe	0

risk mix of the 8 listed

safe75%
caution25%

0 of 8 encrypted

Port :8768Sandpolis Server

Technical Details

Security Information

Related Ports

Port 8768Sandpolis Server