Port 7474Neo4j HTTP

Neo4j's HTTP endpoint serves its browser interface and database APIs, typically on TCP 7474.

transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
8/10

risk

lookups
0

rank 993 of 5,885 · top 17%

also known as Neo4j Browser, Neo4j HTTP API

Technical Details

what runs on :7474

This is Neo4j's HTTP connector over TCP, normally listening on port 7474. Clients speak HTTP, and the endpoint can serve the Neo4j Browser as well as database HTTP APIs; the exact API paths vary by Neo4j version. The separate Bolt protocol, commonly on TCP 7687, uses a distinct binary protocol. HTTPS is typically provided separately on port 7473 when enabled; HTTP on 7474 is not encrypted by default.

Security Information

exposure of :7474

risk score

8/ 10risk

treat as sensitive. widely scanned and regularly exploited when reachable — restrict it to known sources.

web services averages 3.1 across 213 ports — this one sits 4.9 above.

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

An exposed endpoint can reveal the Neo4j Browser and provide a route to query or modify graph data. Authentication and authorization should be enabled and correctly configured, but credentials and database traffic sent over this HTTP endpoint are not encrypted in transit. Do not expose it directly to the public internet; restrict access to trusted networks or use HTTPS through a properly configured connector or reverse proxy.

the 8 most looked-up other ports in web services — 213 ports carry that label.

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted