Port 29900Nintendo Wi-Fi
Nintendo's Wi-Fi Connection (NWC) was an online multiplayer gaming service for the Nintendo DS and Wii consoles. It allowed users to connect globally for gameplay, matchmaking, and content downloads, bridging Nintendo devices to the internet securely and efficiently. Despite its discontinuation, associated ports like 29900 are still relevant for emulator support and private server operations..
- transport
- unknown
- in transit
- cleartext
- assignment
- unofficial
- risk
- 4/10
- lookups
- 6,805
single transport
payload readable on path
used by convention
caution
rank 751 of 993 · top 76%
Technical Details
what runs on :29900Nintendo Wi-Fi Connection was Nintendo’s proprietary online gaming service, designed primarily for Nintendo DS and Wii platforms. It operated through a series of dedicated ports to facilitate matchmaking, gameplay data transmission, and leaderboard updates. Port 29900 was typically used for server listing, matchmaking relay, or client communication, functioning alongside other Nintendo-maintained servers.
The port enabled UDP/TCP traffic when triggered by the application, often within a custom protocol designed by Nintendo to optimize performance on handheld and console hardware with limited networking stacks. This custom protocol included authentication, game session management, and some voice or text chat capabilities depending on the title.
Although the original NWC servers were officially discontinued in 2014, this port remains in unofficial use for private servers and emulation projects that replicate or extend Nintendo Wi-Fi Connection functionality, preserving online features for legacy games via tunnel solutions or community-hosted services.
Security Information
exposure of :29900risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
network services averages 3.9 across 604 ports — this one sits 0.1 above.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
unknown
every listening transport is another surface to filter at the edge
security overview
Common vulnerabilities related to port 29900 usage stem from:
- Open relay possibilities leading to unauthorized server access
- Exploit of weak authentication or absence of encryption
- Use in Distributed Denial-of-Service (DDoS) amplification attacks in community servers
- Impersonation or man-in-the-middle (MITM) attacks during matchmaking
Mitigations include:
- Enabling strict firewall rules limiting access strictly to trusted IP addresses
- Monitoring for unusual traffic patterns or abuse attempts
- Applying network segmentation to isolate gaming servers
- Employing VPN tunnels if used in custom/private setups
- Using reverse proxies or access control lists (ACLs) with authentication requirements in emulator or private server environments
Related Ports
the 8 most looked-up other ports in network services — 604 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :6543 | Jetnet | UDP | Network Services | caution | 65.3k |
| :5938 | TeamViewer | TCPUDP | Remote Access | caution | 65.0k |
| :8291 | Winbox MikroTik Admin | TCP | Security | caution | 62.9k |
| :3233 | WhiskerControl Protocol | TCPUDP | Network Services | caution | 61.9k |
| :3268 | Microsoft Global Catalog (GC) | TCPUDP | Security | caution | 54.6k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :3128 | Tatsoft Default HTTP Proxy | TCP | Web Services | caution | 46.8k |
risk mix of the 8 listed
- caution100%
0 of 8 encrypted