BRev Port 1521 — Oracle Database
Port 1521 is the Oracle TNS listener — a broker rather than the database itself. A client connects, names a SID or service, and the listener hands the session to a database process, sometimes redirecting to another port entirely. That indirection is why Oracle connectivity problems feel different from other databases: the port can be open, the listener healthy, and the connection still fail because the service name is wrong.
It also gives an attacker a free reconnaissance step. A reachable listener answers status queries that enumerate SIDs and service names, which is the first move of every Oracle attack tool, and it historically allowed remote registration of a rogue database — the TNS Poison issue, which permitted man-in-the-middle interception of sessions. Our reference marks it never, and the enumeration alone justifies it.
The right posture is the listener bound to a private interface, valid node checking configured so only known addresses may register or connect, a listener password set, and the whole thing reachable only from application servers. Oracle’s own hardening guidance says the same; the port is a management surface with a database behind it, not a public service.
Port 1521 at a glance
| Field | Value | Detail |
|---|---|---|
| Port | 1521 | Registered |
| Service | Oracle DB | Oracle TNS listener. (TCP) |
| Category | Databases | data stores and their wire protocols |
| Exposure | Never | Never expose to the internet |
Should port 1521 face the internet? Never public; TNS poisoning and SID enumeration are trivial from outside.
Bind it to localhost or a private network. Mass scanners find these within minutes of a host appearing online.
What commonly goes wrong
ORA-12541: TNS:no listener vs ORA-12514: service name not known
Two different stages. 12541 means nothing accepted the connection on 1521 — the listener is down, on another port, or filtered. 12514 means the listener answered and does not know the service you asked for, which is a configuration or name problem, not a network one. Checking the port with the commands on this page tells you which half you are in.
The connection is redirected to a port you did not open
Classic Oracle behaviour: the listener can hand the session to a dispatcher on a different, sometimes dynamic port, so a firewall permitting only 1521 sees the initial connection succeed and the session then fail. Configure a fixed dispatcher port, or use a connection manager, before writing the firewall rules.
Check port 1521 yourself
No browser can open a raw TCP socket, so no web page can honestly tell you whether this port is open on a remote host. These are the real commands, generated for port 1521 — swap example.com for the host you are actually testing.
Is port 1521 reachable on another host?
nc -vz example.com 1521"succeeded!" means the TCP handshake completed — the port is open. "Connection refused" is closed; a hang until timeout means filtered (a firewall dropped it silently).
nmap -Pn -p 1521 example.comThe only common tool that distinguishes open / closed / filtered. -Pn skips the ping sweep, so it still works against hosts that ignore ICMP.
Test-NetConnection example.com -Port 1521Read TcpTestSucceeded: True = open. It is built in — nothing to install.
telnet example.com 1521A blank screen or a banner means it connected. "Connection refused" means closed. Quit with Ctrl-] then `quit`.
curl -v --max-time 5 telnet://example.com:1521Handy when telnet is not installed: "Connected to …" proves the TCP handshake, without curl trying to speak HTTP.
What on this machine is holding port 1521?
sudo ss -tlnp | grep :1521Lists the listening socket and the PID/program holding it. Drop sudo and you get the socket but not the process name.
sudo lsof -i :1521The macOS answer to "address already in use". Kill it with `kill -9 <PID>` once you are sure what it is.
netstat -ano | findstr :1521The last column is the PID. Match it in Task Manager’s Details tab, or `taskkill /PID <pid> /F`.
No web page can tell you whether a port is open on a remote host
A browser cannot open a raw TCP socket — there is no API for it, by design. So a site that reports “port 3389 is OPEN on 203.0.113.10” is not checking from your browser; it is asking its own server to scan on your behalf. That works, but it means their server sees the host you asked about, scans from their address rather than yours, and answers a question about their network path, not yours.
We don't have a server here and won't pretend to. So this page does three honest things instead:
| Port | Proto | Service | What it is | Exposure | |
|---|---|---|---|---|---|
| 1521 | tcp | Oracle DB | Oracle TNS listener.Never public; TNS poisoning and SID enumeration are trivial from outside. | Never |
http://host:port/ and times it. A connection that is established proves a socket is open; an instant refusal usually means nothing is listening; anything else is honestly reported as “can't tell”. Each attempt gives up after 2.5s.nc -vz example.com 443
nmap -Pn -p 443 example.com
telnet example.com 443
curl -v --max-time 5 telnet://example.com:443
This page cannot answer that, and neither can any other page — from your browser. Opening a TCP connection to an arbitrary host and port is not something JavaScript is allowed to do. Every “open port checker” that gives you a green tick is running the scan on their server. Which is fine, as long as you know what you are agreeing to: they learn which host and port you were worried about, and the answer they give you is about the route from their data centre — not from the internet as your users see it.
What to do instead
Run the check from outside your own network. Copy an nmap or nc line from the card above and run it from a machine that is not behind the same router — a phone on mobile data with a terminal app, a cheap VPS, a colleague's laptop. Running it from inside the LAN tests the LAN, not the internet, and will happily say “open” while the world sees nothing.
Then check the thing that is actually blocking it, in this order: the service is bound to0.0.0.0 and not 127.0.0.1 · the host firewall (ufw, firewalld, Windows Defender Firewall) · the cloud security group or the router's port-forward rule · and finally your ISP, which commonly blocks 25, 80 and 445 on residential lines whatever you configure.
What a browser genuinely can verify
One thing: that an HTTPS service answers. If what you actually want to know is “is my site up and how fast is it”, the latency test measures real round trips to a CORS-open URL. If the name doesn't resolve, or resolves somewhere unexpected, that is a DNS problem, not a port problem — and it is the more common cause of “my port is closed” than an actual firewall.
An IP address finds the machine; a port picks which program on it gets the traffic. TCP sets up a connection first — a handshake, ordered delivery, retransmission — which is why the web, email and SSH use it. UDP just sends the packet with no handshake and no guarantee it arrives, which is why DNS, video calls and games use it: late data is worse than lost data.
That difference is why a UDP port is so much harder to test. TCP either completes a handshake or it doesn't, so a tool can tell you. A UDP service that has nothing to say to an unexpected packet stays silent — and silence looks identical to a firewall dropping it.
The three ranges
0–1023Assigned by IANA to core services. On Unix, binding one needs root (or CAP_NET_BIND_SERVICE).1024–49151Registered by vendors for their applications. Any user can bind these — which is why every dev server lives here.49152–65535Never assigned. The OS hands these out as the SOURCE port of your outgoing connections. (Linux actually uses 32768–60999 by default.)Closed is not the same as filtered
Closed means the host answered: the packet arrived, nothing is listening, and you got an immediate refusal (a TCP RST). Filtered means nothing answered at all — a firewall dropped your packet in silence, so you wait for a timeout and learn nothing. The difference matters: closed proves the host is reachable and the port is free; filtered tells you only that something between you and it is discarding traffic.nmap reports the two separately. A browser cannot distinguish them, which is why this page reports a timeout as “can't tell” rather than guessing.
The one habit worth keeping
Bind services to 127.0.0.1 instead of 0.0.0.0 unless something outside the machine genuinely needs them, and reach them over SSH or a VPN. Every database on the never-expose list above ships with that advice, and the leaks all begin the same way: a default bind address, a cloud instance with a public IP, and a scanner that found it within the hour.
The blocked-port list this page uses is the WHATWG Fetch Standard's “bad port” table — the ports every browser refuses to connect to (Chrome calls it ERR_UNSAFE_PORT). Local probing is additionally gated by Chrome's Local Network Access permission, which replaced Private Network Access and ships in Chrome 142.
FAQ
Should port 1521 be exposed to the internet?
No. A reachable listener can be queried for SIDs and service names before any authentication, which hands an attacker the map. Keep it on a private network with valid node checking enabled.
How do I test if the Oracle port is open without an Oracle client?
A plain TCP check is enough to answer the network question — nc, nmap or Test-NetConnection, all generated on this page. They prove the handshake completes; they say nothing about whether the service name is valid, which is the next question.
What is TNS poisoning?
A flaw where an attacker could register a rogue database instance with a reachable listener and have client sessions routed through it, enabling interception. It is the strongest argument for valid node checking and for never exposing the listener.