This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
A port check asks whether a host you operate accepts a connection on a port you name. The ticket has the host and the port. The internet is not the ticket.
UDP answers are easier to misread than TCP. Write what the tool actually showed. A timeout is not always a closed port.
The bulk checker is for a list of your own hosts, such as three lab servers. It is not a way to survey a company, a cloud range, or a customer. Delete any target you do not administer.
Finding a port open is not a reason to try passwords against it. If the port should be closed, the fix is a rule on your device in a later window.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Write one host and one port you operate.
- Run the check.
- Record open, closed, or unanswered.
- If you have a list, confirm every address is yours.
- Do not try to log in.
- Hand a surprise to a firewall ticket.
Mistakes that outlive the command
How to Check if a Port Is Open goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A range you do not run.
- A customer or a neighbour scanned.
- A login attempted because the port was open.
- UDP silence called proof.
- The bulk list left unreviewed.
Decisions to write down
One decision for How to Check if a Port Is Open: Every target is yours. The port is named. The result is one word. No login was attempted. And a surprise becomes a ticket, not a probe.
Checks before you call it done
Confirm this before you call the change done: Host and port are in the ticket. The result is recorded. No foreign range was used. No password was tried. And the next step is a rule change or a stop. If one of those fails, stop.
One host you administer.
No survey of someone else's range.Before you leave the device
How to Check if a Port Is Open ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.