Port 808 occupies an unusual position in the Internet's port system. It sits in the well-known range (0-1023)—the ports supposedly reserved for standardized services assigned by the Internet Assigned Numbers Authority (IANA). But IANA never assigned port 808 to anyone.
So Microsoft took it.
What Lives Here
Port 808 is the default port for Windows Communication Foundation (WCF) Net.TCP services.1 When you install SharePoint Server, configure certain Windows services, or run WCF applications using Net.TCP bindings, they listen on port 808.2
The service that manages this is SMSvcHost.exe—the Net.TCP Port Sharing Service. It allows multiple WCF services to share port 808, similar to how multiple websites can share port 80 through HTTP.sys.3
Intel's Graphics Command Center service (igccservice) also uses port 808, which occasionally causes conflicts when other applications expect it to be available.4
The Well-Known Range
Ports 0-1023 are called "well-known ports" or "system ports." They're supposed to be assigned by IANA to specific, standardized services. Port 22 is SSH. Port 80 is HTTP. Port 443 is HTTPS.
But port 808? The IANA registry lists it as "Unassigned."5
This doesn't mean it's unused. It means no standards body ever claimed it for a specific protocol. It's a gap in the bureaucracy—and gaps get filled by whoever shows up.
Why Unassigned Ports Matter
The port system only works because most applications respect the assignments. When everyone agrees that port 25 is for email and port 53 is for DNS, devices can find each other without negotiation.
Unassigned ports serve a different purpose. They're available for:
- Custom applications that need a predictable port but don't require global standardization
- Internal services that only matter within an organization
- Development and testing where developers need a port that won't conflict with production services
- Proprietary protocols like Microsoft's Net.TCP that serve a specific ecosystem rather than the entire Internet
Port 808 became Microsoft's Net.TCP port not through any RFC or standards process, but through deployment. Enough Windows servers listen on port 808 that it's become an unofficial standard within that world.
How to Check What's Listening
On Windows, you can see what's using port 808:
On Linux or macOS:
If you see SMSvcHost.exe or igccservice, you're looking at Microsoft's claim on this unassigned space.
The Gap Between Official and Real
Port 808 is a reminder that the Internet doesn't run purely on standards. Official assignments matter, but so does what people actually deploy.
The IANA registry is the map. Port 808 is the territory the map left blank—and someone built a city there anyway.
Byla tato stránka užitečná?