Skip to main content
protocols.pageprotocols.page
9800

Port 9800 – WebDAV / Development

TCP

Port 9800 is used by various WebDAV implementations, development servers, and application-specific services. No single dominant service owns this port. When encountered, identify the specific application via service fingerprinting (nmap -sV). Apply standard HTTP security practices.

Port Number

9800

Protocol

TCP

Service

WebDAV / Application Alternate

Range

IANA Registered (1024–49151)

Description

Port 9800 appears in diverse contexts: some WebDAV servers, development environments, and proprietary applications use it as an HTTP alternate. Unlike well-known ports with a single dominant service, port 9800 requires fingerprinting to determine what is running. Treat any unknown service on port 9800 as a potential HTTP endpoint until proven otherwise. Common discovery approach: try an HTTP GET, check for TLS, and use nmap service detection. If it responds to HTTP, apply standard web security assessments (authentication, input validation, TLS configuration).

Security risks

  • 1Unknown service identity – port 9800 has no dominant service, making security assessment impossible without fingerprinting. Treat as hostile until identified.
  • 2WebDAV PUT/DELETE exposure – if a WebDAV server is running, misconfigured access control allows arbitrary file upload (webshell deployment) or deletion.
  • 3Development server leakage – applications binding to 9800 during development often lack auth, expose debug endpoints, and serve source maps or stack traces.

Firewall guidance

Block inbound 9800 by default. If a service requires it, identify the service first (nmap -sV), then apply service-specific hardening. For WebDAV, require authentication and restrict HTTP methods to GET/PROPFIND unless write access is intentional.

Diagnosis commands

Fingerprint the service – identify what is actually listening on port 9800

shell
nmap -sV -p 9800 target

Check for HTTP response headers that reveal the server software

shell
curl -v http://host:9800/ 2>&1 | head -20

Enumerate allowed HTTP methods – look for PUT/DELETE indicating WebDAV write access

shell
curl -X OPTIONS http://host:9800/ -i

Usage examples

Port 9800 – WebDAV / Development
shell
nmap -sV -p 9800 target (service fingerprinting)
curl -v http://host:9800/ (test HTTP response)
curl -X PROPFIND http://host:9800/ (test WebDAV)

Common services on this port

WebDAV serversapplication development serversproprietary admin interfaces

Related ports

80

HTTP (standard web)

443

HTTPS (standard secure web)

8080

HTTP alternate (common dev port)

History

Port 9800 has no single RFC assignment. It appears in IANA as unassigned and has been adopted by various applications including some WebDAV implementations and development frameworks. Its use is entirely convention-driven within specific software ecosystems.

FAQ

What service uses port 9800?

No single dominant service. Common candidates include WebDAV servers, development/staging instances of web applications, and proprietary software. Use nmap -sV -p 9800 to fingerprint what is actually running.

Is port 9800 safe to expose?

Not without knowing what is running. Fingerprint first, then apply service-specific security controls. If it is a development server, it should never be exposed – bind to localhost only.