You’ve landed on localhost9200.com

You probably meant http://localhost:9200

That’s a port on your own machine — where Elasticsearch and OpenSearch listen by default — not a domain on the public internet. The colon is the whole difference.

Open http://localhost:9200 →

What is port 9200?

Port 9200 is the default HTTP port for both Elasticsearch and OpenSearch — the REST API your code, curl, and dashboards talk to. Start a node locally with the default settings and it listens on http://localhost:9200.

Its usual sibling is port 9300, the transport port that nodes use to talk to each other inside a cluster. You almost never open 9300 in a browser — if you were reaching for the API, 9200 is the one you want.

Stop your browser suggesting this domain

Now that you’ve been here, your browser has learned localhost9200.comand will keep offering it. Here’s how to delete that one suggestion — without wiping the rest of your history.

Chrome, Edge & other Chromium browsers

  1. Start typing localhost9200 in the address bar until the suggestion appears.
  2. Press the ↓arrow to highlight it (don’t press Enter).
  3. Press Shift + Delete — on a Mac, Shift + Fn + Delete. Recent versions also show a Delete option when you hover the suggestion.

Firefox

  1. Type localhost9200 until the suggestion shows in the drop-down.
  2. Press ↓ to highlight it.
  3. Press Shift + Delete, or click the three-dot button on the suggestion and choose Remove from history.

A starred suggestion is a bookmark and won’t delete this way — remove the bookmark instead.

Safari

Safari has no per-suggestion shortcut; it offers the site because it’s in your history. Remove the underlying entry:

  1. Open History → Show All History (⌘ + Y).
  2. Search for localhost9200, then Control-click the entry and choose Delete.
  3. If it also sits in your Favourites or Frequently Visited, Control-click that tile and choose Delete.

To stop suggestions entirely, see Safari → Settings → Search. Full steps: Apple Support.

Common development ports

A quick reference for the ports you’re most likely to be reaching for. Defaults can be changed, but these are what each tool ships with.

Default ports for common development tools
PortTypicallyNotes
3000Node.js / Next.js / React devnext dev, Create React App, and many Node dev servers start here.
4200Angular CLIThe Angular CLI ng serve development server.
5173ViteThe Vite dev server default (Vue, React, SvelteKit, and others).
5432PostgreSQLDefault PostgreSQL database port.
6379RedisDefault Redis port.
8000Django / PythonDjango runserver and Python’s http.server default here.
8080Tomcat / generic HTTPApache Tomcat’s default HTTP connector; a common generic HTTP alternate.
9200Elasticsearch / OpenSearch (HTTP)The REST API — the one you almost certainly wanted.
9300Elasticsearch / OpenSearch (transport)Node-to-node transport inside a cluster; not for browsers.
27017MongoDBDefault MongoDB (mongod) port.

Local server on 9200 not responding?

You’re back at http://localhost:9200but it still won’t load. Work down this list — it’s roughly ordered from most to least common.

Is the server actually running?
The most common cause: nothing is listening yet. Start your node and check the terminal for errors, then confirm with curl http://localhost:9200.
Port already in use?
Another process may already hold 9200, so your node grabbed the next free port (9201, 9202…). Elasticsearch and OpenSearch bind the first open port in the 9200-9300 range. Check with lsof -i :9200 (macOS/Linux) or netstat -ano | findstr 9200 (Windows).
Bound to the wrong address?
By default a node binds to loopback only. If you’re reaching it from another machine or a container, set network.host (or http.host) appropriately — and remember that 0.0.0.0 exposes it on every interface.
HTTP vs HTTPS?
Since version 8.0, Elasticsearch turns on TLS by default, so the API speaks https://localhost:9200, not http. Your browser will warn about the self-signed certificate on first visit — that’s expected locally.
Getting a 401 / auth prompt?
Elasticsearch 8.0+ also enables authentication by default, so an unauthenticated request gets a 401. Use the elastic user with the password (or enrollment token) printed once on first startup; regenerate it with bin/elasticsearch-reset-password.
Firewall or container in the way?
A local firewall, VPN, or container port mapping can swallow the connection. If you’re in Docker, make sure you published the port (-p 9200:9200).