Is port 28017 (MongoDB HTTP Status) dangerous?

Port 28017 is classified as critical risk and should not be exposed to the public internet. It transmits data without encryption, making it vulnerable to eavesdropping and credential theft.

Should port 28017 be open on my firewall?

No, port 28017 should not be open to the public internet. Block it at the firewall and use encrypted alternatives such as SSH, SFTP, or HTTPS instead.

What transport protocol does port 28017 use?

Port 28017 (MongoDB HTTP Status) uses the TCP transport protocol and falls under the Database category.

:28017 (TCP)

MongoDB HTTP Status

Critical Risk

TCP — Database

Port Overview

Port Number 28017

Service Name MongoDB HTTP Status

Transport Protocol TCP

Category Database

Security Risk Critical

Port Range Registered (1024-49151)

What is Port 28017?

Previously used by MongoDB for its built-in HTTP status interface and REST API, deprecated in MongoDB 3.2 and removed in 3.6. Historically exposed database statistics and admin information over HTTP without authentication. Should be blocked on any legacy MongoDB deployments.

TCP Database

Security Considerations

Port 28017 (MongoDB HTTP Status) is classified as critical risk. This port should not be exposed to the public internet. The service transmits data without encryption, making it vulnerable to eavesdropping, credential theft, and man-in-the-middle attacks.

Recommendation: Block this port at the firewall. Use encrypted alternatives (SSH, SFTP, HTTPS) instead.

Related Ports — Database

66 Oracle SQL*NET 118 SQL Services 134 INGRES-NET 142 BL-IDM 150 SQL-NET 156 SQL Service 181 Unify 188 MUMPS

Related Terms

ASN BGP Hijack Data Center Domain Name Dual Stack Internet Exchange Point (IXP)