Skip to content
AdminKit

Port check for exposed cameras and routers: Telnet, RTSP and more

To port check your cameras and routers, open AdminKit's free port check from a device on that network. It tests your own public IP from outside. If port 23 (Telnet), 554 (RTSP), 7547 (TR-069) or 8080 (web admin) shows open, anyone online can reach that service: remove the port forward or put access behind a VPN.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • Telnet (port 23) is a plaintext admin shell; RTSP (port 554) controls live camera video. Cheap routers, cameras, DVRs and NVRs often ship with both enabled.
  • The Mirai botnet grew by logging in to exposed Telnet ports with a short list of default passwords, with no exploit needed.
  • RTSP leaves authentication to the device; some cameras stream to anyone who knows the URL.
  • Fix it by turning Telnet off, setting stream credentials, and replacing port forwards with a VPN for remote viewing.
  • To check your own devices, run AdminKit’s free port check from the same network and read ports 23, 554, 7547 and 8080.

How do I port check my cameras and routers?

A port is a numbered door on a device that one network service listens on. A port check asks which of those doors answer from the internet. Here is how to run one on your own network with AdminKit:

  1. Connect from the network you want to test. Use a phone or laptop on the same Wi-Fi or office network as the camera or router. Turn off any VPN on that device first, or the check will test the VPN’s address instead.
  2. Open the port check and start it. It only tests the public IP your request comes from, and only after you click. The connection attempts come from AdminKit’s side, so they show what a stranger on the internet would see.
  3. Read the four camera and router ports below. The check also covers 80, 443, 502, 1883 and 8883; the guide to reading a port check result explains all nine.
  4. Fix what is open, then run the check again to confirm the port now shows closed/filtered.

“Open” means something accepted a TCP connection. “Closed/filtered” means the connection was refused or got no answer; the check cannot tell those two apart. It never tries a password or sends commands. The port numbers below are the IANA-registered defaults, so a device moved to a different port is not covered.

Result from the port checkWhat it usually meansWhat to do
Port 23 (Telnet) openA router, camera or recorder offers a plaintext admin shell to anyoneRemove the port forward, turn Telnet off, change the admin password. See is port 23 (Telnet) exposed?
Port 554 (RTSP) openA camera or recorder’s video stream control is reachableRemove the port forward and confirm the stream asks for credentials (see the curl test below). See is port 554 (RTSP) exposed?
Port 7547 (TR-069) openThe router’s remote management channel, often used by the ISP, answers from outsideIf the ISP supplied the router, ask them whether it must stay open, and keep the firmware updated. See is port 7547 (TR-069) exposed?
Port 8080 openOften a router, camera or recorder web admin page on an alternate HTTP portTurn off remote (WAN-side) admin or remove the forward. See is port 8080 (admin panel) exposed?
All four closed/filtered, but the camera app still works remotelyThe vendor’s cloud relay probably carries the videoCheck the vendor account’s password and two-factor settings
All closed, and your connection uses CGNATYour router has no public address of its ownStill fix the device settings; see the CGNAT note at the end

Ports open that you never forwarded usually come from UPnP, which lets devices open router ports by themselves. For a business with more than one site or device class, the network hygiene checklist for small business puts this check in order with remote desktop, file sharing and IoT devices.

Why do Telnet and RTSP show up on the same devices?

Telnet and RTSP have nothing in common at the protocol level — one is a remote text shell, the other is a video streaming control protocol — but they show up together constantly on the same class of devices: home routers, IP cameras, DVRs and NVRs. Both were designed decades ago for trusted, closed networks, and both are still commonly shipped turned on by default on cheap embedded hardware, because removing them or replacing them with an authenticated, encrypted alternative costs engineering time that low-margin consumer device manufacturers often don’t spend.

TelnetRTSP
StandardRFC 854RFC 7826 (RTSP 2.0)
Default port23/tcp554 (322 for RTSP over TLS)
What it gives access toA command-line admin shellControl of live audio and video streams
EncryptionNoneOnly when run over TLS
AuthenticationLeft to the device’s login promptLeft to the device; HTTP-style schemes such as Digest are defined
Main risk when exposedDevice takeover with default credentialsAnyone viewing the camera feed

What makes an exposed Telnet port dangerous?

RFC 854 defines Telnet as exactly what its name suggests — a protocol for remote terminal access. It sends everything, including any password you type, as unencrypted plaintext over the network, and its authentication (where it exists at all) is often a hardcoded or weak default credential set by the manufacturer rather than something the end user is prompted to change. That combination — administrative access, no encryption, predictable credentials — is precisely why Telnet-scanning became the foundation of one of the most consequential botnets in internet history.

The academic analysis of the Mirai botnet presented at USENIX Security 2017 documented the mechanism directly: Mirai “statelessly sent TCP SYN probes to pseudorandom IPv4 addresses… on Telnet TCP ports 23 and 2323,” then attempted logins using a dictionary of 62 common username and password pairs aimed specifically at consumer routers and IoT devices. Every successful login added one more device to the botnet, with no exploit required beyond a default password nobody had changed.

Two lessons from that analysis apply to any device owner today. First, the scanning was random: Mirai didn’t pick targets by who owned them, so being a small home network or an unremarkable business offered no protection. Second, it probed port 2323 as well as 23, because some devices run Telnet on that alternate port. When you check your own equipment, test both ports, and treat any login prompt answering on either one from outside your network as something to fix the same day.

How can an RTSP camera stream end up public?

RTSP (Real-Time Streaming Protocol, see glossary definition), standardized in RFC 7826 (also on the IETF Datatracker), is how a huge share of IP cameras and DVRs negotiate and control a live video stream. The protocol itself has no opinion on authentication or encryption — that’s left to the implementer — and in practice, a large number of camera firmware images expose an RTSP endpoint that streams video to anyone who knows (or guesses) the right URL path, sometimes with no credential check at all. Search engines that index internet-facing devices routinely turn up thousands of such feeds: home camera streams, retail store interiors, parking lots, left reachable because the installer connected the camera to the internet for remote viewing convenience and never locked down who else could view it.

RFC 7826 does define how a server should challenge a client: it answers 401 Unauthorized with a WWW-Authenticate header naming a scheme such as Digest, and the client retries with credentials. Whether a given camera actually sends that challenge is up to its firmware. You can see which behaviour your own camera has from a machine on your LAN, using curl’s RTSP support. The address and path below are examples; stream paths differ by vendor and are listed in the camera’s manual:

$ curl -i --rtsp-request DESCRIBE rtsp://192.168.1.30:554/stream1
RTSP/1.0 401 Unauthorized
CSeq: 1
WWW-Authenticate: Digest realm="camera", nonce="..."

A 401 with an authentication header is what you want. A 200 OK followed by a session description (lines starting with v=, m=video) means the camera hands out its stream with no credentials at all. If so, look for a stream-authentication setting in the camera’s web interface; if there isn’t one, keep that camera strictly on an isolated segment.

Why do these ports end up reachable from the internet?

Three common paths lead to an exposed Telnet or RTSP port:

  • The manufacturer’s default configuration binds the service to all network interfaces, not just the local network, so the moment the device gets a routable address it’s reachable.
  • A user or installer forwards the port on their router specifically to enable remote camera viewing or remote admin access, without realizing that forwarding also exposes it to the entire internet, not just their own remote device.
  • The device sits directly on a public IP with no router or firewall in front of it at all — more common for business or industrial deployments than home ones, but it still happens.

How do you check and fix it?

  1. Confirm your actual public-facing IP. Use AdminKit’s what is my IP tool to see the address your network presents to the internet — this is the starting point for any exposure check, including deciding what to test next.
  2. Test whether the ports actually respond from outside. Run the port check as described above. A port that answers when it shouldn’t is the exposure itself, independent of whether anyone has exploited it yet.
  3. Disable Telnet entirely if the device offers any alternative. Most modern router and camera firmware includes an SSH-based or web-based admin interface instead; use that and turn Telnet off in settings, not just change its password.
  4. Change every default credential, on both the Telnet admin account and the RTSP stream’s viewing credentials if the device supports one — a disabled-by-default feature re-enabled with a default password buys you nothing. In the UK, the consumer connectable product security regime, in force since 29 April 2024, requires such products’ passwords to be unique per product or capable of being defined by the user.
  5. Put remote access behind a firewall rule or VPN rather than a direct port forward. If you genuinely need to view a camera remotely, a VPN back into your own network keeps the RTSP stream itself off the public internet entirely, closing the exposure without losing the feature.

What does a safer camera setup look like?

Most of the risk on this page comes from cameras and recorders sharing a flat network with everything else and reaching the internet directly. A layout that limits it, without losing remote viewing:

  • Put cameras and the recorder on their own network segment, such as a separate VLAN or a dedicated guest-style network, so a compromised camera can’t reach laptops or file shares.
  • Let the NVR or DVR pull streams locally and keep the cameras themselves unreachable from outside. Remote viewers then connect to one well-maintained device rather than to each camera.
  • Reach that recorder through a VPN into your own network rather than a port forward.
  • Block outbound internet access for cameras that don’t need it. A camera that only streams to a local recorder has no reason to talk to the internet, and blocking it also stops it reaching out on its own.
  • Turn off UPnP on the router if nothing depends on it, so devices can’t open their own port forwards. Our guide to mDNS, SSDP and UPnP discovery leaks explains how that happens.

For the Telnet side in more depth — moving to SSH, and what to do with devices that can’t — see securing an exposed Telnet device.

Is your network even reachable from the internet?

Whether an open Telnet or RTSP port is actually dangerous also depends on whether your network is reachable from the public internet the way you think it is. If your ISP uses Carrier-Grade NAT, your router may not have a direct, stable public IP at all — see our CGNAT guide for what that means and how to check it. It’s not a substitute for disabling these services properly, but it’s useful context before assuming a given result means what it looks like at first glance.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

Why does Telnet still exist on modern devices?

Telnet (defined in RFC 854) predates the modern internet and was simply never retired from many embedded device firmware images, because it's cheap to implement and manufacturers prioritize working remote administration over security during development. It was never designed with encryption or strong authentication in mind.

Is RTSP itself insecure, or just how it's usually deployed?

RTSP (RFC 7826) is a streaming control protocol, not an encryption standard — it was designed to negotiate and control a media stream, and by default that stream and its control channel are unauthenticated and unencrypted. The insecurity comes from devices exposing it directly to the internet with default or no credentials, not from a flaw unique to RTSP itself.

What can an attacker actually do with an exposed Telnet port on a camera or router?

If the device still uses a default or weak password — extremely common on consumer IoT hardware — an attacker gets a full administrative shell: they can read configuration, change DNS settings, install malware, or recruit the device into a botnet. The 2017 academic analysis of the Mirai botnet documented exactly this pattern at internet scale.

What can an attacker do with an exposed RTSP stream?

At minimum, unauthorized viewing of whatever the camera sees — a real privacy problem for a home or office camera. Some RTSP implementations have also had separate authentication-bypass or buffer-overflow vulnerabilities, so an exposed stream can be a foothold into the device itself, not just a video feed.

How do I check whether my own camera or router has these ports open?

Open AdminKit's free [port check](/tools/port-check/) from a phone or computer on the same network as the camera or router. It tests the public IP your request comes from on nine TCP ports, including 23 (Telnet), 554 (RTSP), 7547 (TR-069) and 8080 (web admin). Any of those shown as open, unless you deliberately set it up, should be treated as exposed and fixed.

Why does the port check show a port open that I never forwarded?

Usually because UPnP on the router let a device open the port by itself, because the ISP manages the router remotely (port 7547), or because the router's own web admin is enabled on its internet side (often port 8080). Log in to the router, check its port forwarding and UPnP tables and its remote management settings, then run the check again.

Is disabling Telnet and RTSP enough to secure a camera?

It closes the two most common unauthenticated entry points, but it's one part of a broader checklist — also change default credentials everywhere, keep firmware updated, and put the device behind a firewall or VPN rather than forwarding its ports directly to the internet.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.