Eberprot P / tools

Tools

Most everyday checks don't need third-party software: the utilities you need are already on your system. For each one we cover its purpose, input, limitations, difficulty level and an example.

Examples marked "Tested by our editors" were run on Ubuntu 24.04.5 LTS; output is shortened. Our test environment has no access to external network addresses, so those examples are based on documentation.

Difficulty: Beginner

sha256sum / Get-FileHash

Purpose
Calculate a file's checksum and compare it with a published or previously saved one.
Input
A file path; for verification, a file containing a list of checksums.
Limitations
Confirms that the contents match, not that the file is safe: a malicious file has a valid checksum too.
Example
Tested by our editors
printf 'hello\n' | sha256sum
5891b5b522d5df086d0ff0b110fbd9d21bb4fc7163af34d08286a2e846f6be03  -
Learn more: How-to guides
Difficulty: Beginner

ping

Purpose
Check whether a host on the network responds, and with what latency.
Input
An IP address or domain name.
Limitations
Many servers deliberately don't respond to ping — no reply doesn't necessarily mean the host is unreachable.
Example
Based on documentation, not tested
ping -c 4 1.1.1.1
Learn more: Troubleshooting
Difficulty: Intermediate

traceroute / tracert

Purpose
Show the path packets take to a host and where the connection breaks.
Input
An IP address or domain name.
Limitations
Intermediate routers often don't respond — lines with asterisks are normal.
Example
Based on documentation, not tested
traceroute example.com
Learn more: Troubleshooting
Difficulty: Intermediate

nslookup

Purpose
Find out which IP address DNS resolves a domain name to.
Input
A domain name; optionally, the address of a specific DNS server.
Limitations
Shows the answer from one particular DNS server; your browser and system caches may differ.
Example
Based on documentation, not tested
nslookup example.com
Learn more: Glossary
Difficulty: Intermediate

curl -I

Purpose
View a website's HTTP status and response headers: 200, 301, 404, 410.
Input
The full page address.
Limitations
A site may respond differently to different clients; redirects aren't followed by default (add -L).
Example
Based on documentation, not tested
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/
Learn more: Glossary

Which tool to use

TaskToolWhere it's covered
Check a downloaded file or a backupsha256sum / Get-FileHashHow-to guides
Find out whether you're connected to the internetpingTroubleshooting
Find where the connection breakstraceroute / tracertTroubleshooting
A site loads for others but not for younslookupGlossary: DNS
Check whether a page returns 200 or a redirectcurl -IGlossary: HTTP status

Sources and verification

Software and service interfaces change. We list the versions we tested commands on; on other versions the steps may differ.