Ahom Cybersecurity logo Ahom CybersecurityPlain-language security for people and small teams
Tools and Software

How to Check Your Home Network for Open Ports Safely

A reader sent me a screenshot last year of a scan showing port 32400 open on his home connection. He did not recognise it.

A laptop showing a router port forwarding page with several old rules listed, beside a home router with blinking status lights

A reader sent me a screenshot last year of a scan showing port 32400 open on his home connection. He did not recognise it. It was Plex, which he had set up in 2019, used for about four months, and then forgotten when the old machine went in a cupboard. The machine was still running. It had not been updated in roughly five years, and it was answering requests from the open internet.

That is the shape this problem usually takes. Nobody deliberately exposes their home network. They open one port for a game server, a camera, a media server or a work laptop, and then the reason for it disappears while the rule stays. I have found three of my own, including a rule I created in 2021 for a Minecraft server that lasted one weekend.

First, check whether you are reachable at all

A lot of people spend an hour on this before discovering their connection cannot be reached from outside in the first place. Many mobile and fibre providers now put customers behind carrier grade NAT, which means your router does not hold a public address and nothing on the internet can initiate a connection to it.

The test takes thirty seconds. Log into your router and find the WAN or Internet status page, then note the IP address it shows. Now visit any site that tells you your public IP and compare. If the two match, you have a public address. If the router shows something starting with 100.64 through 100.127, or a 10. or 192.168. address, you are behind your provider's NAT.

Behind CGNAT, your forwarding rules do nothing and an external scan will show nothing, which is a kind of accidental protection. It is not a reason to skip the rest of this, because the rules are still sitting there waiting for the day your provider gives you a public address or you switch to a plan that includes one.

Scanning from outside, and reading the result

The tool I still point people at is Shields Up, run by Gibson Research, because it is free, needs nothing installed, and scans the address you are connecting from. Run the common ports test first, which covers the couple of dozen that matter most, then the full service ports scan if you want the long version.

The results come back in three states and the labels cause confusion. Open means something answered, and that is the only one you need to care about. Closed means your router replied with a refusal. Stealth, or filtered, means it did not reply at all.

Plenty of guides treat anything less than all stealth as a failure. I disagree, and this is the one piece of received wisdom I would push back on hardest. A closed port is not a vulnerability. The refusal packet tells an attacker your address is in use, which they can work out from a dozen other signals anyway. Chasing a perfect stealth result usually means turning on a setting that drops ICMP, which then breaks your ability to diagnose your own connection later. I have done this and spent a tedious evening working out why nothing responded to a ping.

What matters is the open list. Anything on it should map to something you deliberately run and can name.

The forwarding table is where the truth lives

An external scan tells you what is reachable right now. The forwarding table tells you what your router has agreed to allow, which is a longer and more interesting list. On most routers it sits under a heading like Port Forwarding, Virtual Server, NAT Forwarding or Applications and Gaming.

Go through it line by line. For each rule, ask what device it points to, whether that device is still switched on, and whether you still use the thing it was for. Delete anything you cannot answer all three for. Nothing bad happens if you remove a rule you still needed, because the service simply stops working from outside and you add it back.

PortWhat it usually isWhat to do
22SSH, often a home server or NASKey only login, or reach it through a VPN instead
23Telnet, usually on old hardwareClose it, and replace the device if it needs telnet
80 and 443A web interface, sometimes the router itselfClose unless you knowingly host something
445Windows file sharingNever expose this, no exceptions
554Camera video streamClose, use the vendor app or a VPN
3389Remote DesktopClose, this is a routine target for guessing attacks
5900VNC remote controlClose, and check it has a password at all
32400Plex media serverKeep only if the server is patched and you use it

Two other router settings belong in the same pass. Look for Remote Management, Remote GUI or Web Access from WAN, and confirm it is off. That setting exposes your router's own admin page, and routers are a popular target precisely because their firmware is often years behind. Also check for a DMZ host, which forwards everything to one machine. If a DMZ address is set and you did not set it, that is the first thing to clear.

UPnP and the ports you did not create

Universal Plug and Play lets a device on your network ask the router to open a port for itself, without asking you. Consoles use it. So do some games, some cameras, and a fair amount of malware.

Most routers have a page showing current UPnP mappings, sometimes called UPnP Port Map Table. Look at it. The list changes through the day, which is the point: a scan at 10:00 and a scan at 21:00 can give different answers because a console asked for something in between. That is also why a single clean external scan proves less than people think.

I leave UPnP on at home, because turning it off means manually forwarding ports for a console and I know I will get that wrong. What I do instead is check the mapping table every few months and look for anything pointing at a device that should not be asking. On a network with cameras or older smart plugs, I would turn UPnP off and accept the inconvenience.

The gap nobody mentions, which is IPv6

Here is the part that makes a clean scan less reassuring than it looks. IPv6 does not use NAT. Every device on your network can have a globally routable address, and the only thing between those devices and the internet is the router's IPv6 firewall.

So you can have an empty forwarding table, a perfect stealth result on the IPv4 scan, and a laptop or a NAS directly reachable over IPv6. Shields Up scans the IPv4 address you present, so it will not see any of this. Find the IPv6 firewall setting in your router, usually under the IPv6 section, and confirm it is enabled and set to block unsolicited inbound connections by default. On most consumer routers it is, but I have seen two models from the same vendor ship with it off.

The device level firewall is your backstop for all of this, which is why it is worth checking that it is actually on and configured. If you have never looked, start with setting up your computer firewall. And if you are doing this on a new router, the first twenty minutes of setting one up securely covers the admin password and firmware steps that come before any of this. More tool walkthroughs sit in tools and software.

Frequently asked questions

How do I check for open ports on my home network?

Run a free external scan such as Shields Up to see what answers from the internet, then open your router's port forwarding page and review every rule. The external scan shows what is live, the forwarding table shows what is permitted.

Is it bad to have closed ports rather than stealth ports?

No. Closed means your router actively refused the connection, which is a normal and safe result. Only open ports need attention. Chasing an all stealth result often means disabling diagnostics you will later want.

Should I turn off UPnP on my router?

Turn it off if your network includes cameras, older smart devices or anything you do not trust, since those are the devices most likely to request a mapping you did not want. With only consoles and PCs, reviewing the mapping table a few times a year is a reasonable middle ground.

Why did my scan show nothing open at all?

Usually because you are behind your provider's carrier grade NAT, so your router has no public address. Compare the WAN address on your router with the public address a lookup site reports. If they differ, that is the reason.

TL
Tobias Lund

Tobias explains how networks, devices, and the tools that protect them work, aimed at people setting things up for the first time.

More posts by Tobias

More in Tools and Software

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto