ServerNet Tools: A Precise Reference for Inputs, Outputs, and Limitations

Get to know each ServerNet tool by its input, output, limitations, and where it runs (browser or server), so you know which tool is precise for which job and where it will mislead you.

6 min Updated 22 Nov 2026

Looking for an online tool and not sure which one gives an accurate answer? The usual problem is that most lists only name the tools and don't say what you give them, what you get back, and where they fall short. This article fills that gap: for each ServerNet tool, we spell out the input, output, real limitations, and where it runs. If you want the exact value or the official definition, this is the place.

Where ServerNet tools run: browser or server

This distinction is the most important thing to know before anything else, because it determines where your data goes and how reliable the result is.

  • Browser-side: Tools like timestamp conversion, Base64 decoder, UUID generation, and subnet calculator. Your input never leaves your device. The output is instant and doesn't depend on the network. Limitation: if the browser is old or JavaScript is disabled, the tool won't work.
  • Server-side: Tools like WHOIS lookup, DNS record lookup, SSL test, and ping. The request goes out from the ServerNet server and the response comes back. Limitation: the result depends on the network path the server sees, not the network path you see.

This one point resolves half of all confusion. If the DNS test result differs from what you see on your own device, first ask which resolver the tool queried.

DNS and network tools: input, output, and limitations

This category is the most useful for troubleshooting and also creates the most misunderstanding. The full list is in DNS and network tools; here we pin down the behavior of each one.

DNS record lookup

Input: domain name and record type (A, AAAA, MX, TXT, CNAME, NS). Output: the record value along with the TTL. Limitation: the tool queries its own resolver, so if the TTL is high you may see a cached version rather than the fresh record. To see the final value from the authoritative source, you must query the domain's nameserver directly:

dig @ns1.example.com example.com MX +noall +answer

If the dig output differs from the web tool, it's almost always a caching issue, not a DNS failure.

Domain WHOIS lookup

Input: domain name. Output: registrar, registration date, expiration date, EPP statuses, and nameservers. Limitation: for .ir domains the response structure differs from gTLDs and some fields may be redacted. If you want to know how the expiration date is read and which status means the domain is at risk, see the complete guide to domain WHOIS lookup.

SSL and port check

Input: domain or IP, port number. Output: certificate chain, expiration date, signature algorithm, port open status. Limitation: the tool only looks from the outside. If port 443 is open from inside the network but closed from outside, the issue is a firewall or NAT, not the service. For interpreting common errors like certificate has expired or unable to get local issuer certificate, the guide to network checks and SSL, port, and DNS troubleshooting explains it in more detail.

Webmaster tools: which number to take seriously

This is where you'll find more misleading numbers than anywhere else. The collection is gathered in webmaster tools.

ToolInputOutputMain limitation
Website speed testURLTTFB, full load time, page sizeDepends on the test server's location; not an absolute number
Redirect checkURLChain of 301/302 codes and final destinationShows a redirect loop to some extent, but not its cause
Hash generationText or fileMD5, SHA-1, SHA-256Browser-side; slows down for large files
Timestamp conversionUnix number or dateUTC and local timeYou must select the time zone yourself

A TTFB under 200 milliseconds is usually healthy; above 600 milliseconds means you should look at the database and caching, not the site template. But this threshold also depends on the geographic distance between the tester and the server.

This is where people go wrong

A common mistake I've actually seen: someone runs an SSL or DNS test on a domain that hasn't yet been migrated to the new server, sees the old number, and starts changing the new server's config. Two hours later everything falls apart, because the problem was never on the server.

The sign is this: the tool says the certificate is expired, but on the server openssl x509 -enddate -noout -in /etc/letsencrypt/live/example.com/fullchain.pem shows a valid date. Or the tool returns the old IP while the zone has just been updated. At that moment, stop and check propagation first, not the config.

Tools that stay browser-side and why it matters

Converters, decoders, UUID generators, and subnet calculators send no data to the server. This means you can put a key or token into them without it being recorded anywhere. But there's a cost: if you close the browser, the result is gone and there's no history. For repetitive work, a local script is better than a web tool.

By contrast, server-side tools are great for one-off tasks and bad for continuous monitoring. If you want to check SSL status every five minutes, a web tool won't do; you need to set up a cron job:

echo | openssl s_client -servername example.com -connect example.com:443 2>/dev/null | openssl x509 -noout -dates

Which tool should I choose

If you want just one piece of advice: for DNS troubleshooting, always start from the authoritative source, not the web tool. The web tool is good for a first look, but the definitive answer comes from dig querying the nameserver directly. For SSL it's the opposite: the web tool that looks from the outside sees exactly what the user's browser sees, and that's more valuable.

And if the site is on shared hosting and you have little control over the config, server-side tools will serve you better than tinkering with system files. On Linux hosting this path is usually shorter: external tool first, then the server log.

For cases the web tools don't cover, such as process modeling or setting up internal services, separate documentation has been written: the BPMN designer guide for process modeling, setting up a cloud phone for business, and setting up a remote desktop with RustDesk. The rest of the list is in the documentation and knowledge base, and analytical content is in the ServerNet blog.

Frequently asked questions

Do ServerNet tools store the data I enter?

Tools that run browser-side send no data to the server at all, so there's nothing to store. Server-side tools like WHOIS and DNS only receive the query parameter and return the result. For sensitive data, always choose the browser-side tool.

Why does the DNS test result differ from what I see on my system?

Because each queries a different resolver, and the record's TTL causes caching. The web tool queries its own resolver and your system queries the ISP's or router's resolver. To see the definitive value, query the domain's nameserver directly with dig @ns1.example.com.

How reliable is an online SSL test?

It's reliable for seeing the certificate chain and expiration date, because it sees exactly what the user's browser sees. But it's not enough for troubleshooting the server's internal configuration; you should also check the web server log and the certificate file on the server itself.

Do webmaster tools give correct numbers for Iranian websites?

The TTFB number and load time depend on the test server's location, so if the test server is outside Iran, you'll see a higher number than the actual experience of an Iranian user. For comparison, always use a fixed test point and don't compare two numbers from two different locations.

Was this page helpful?