Command line
srvs: server, website, DNS and email checks from the command line
A free, open-source program for Linux, macOS and Windows that runs the same checks as our online tools, from your own machine.
Latest version: 0.1.1 (released 13 October 2026; what changed). Free and open source under the MIT licence: source code, release notes and checksums are on GitHub. Every check is also available as a free online tool.
Seen srvs-cli in your server logs?
Requests with the user agent srvs-cli/0.1.1 (+https://srvscripts.com/cli/) come from someone who ran srvs on their own computer to check a website, a mail server or a certificate. The program makes one request per check, like a browser or curl, and does not crawl. The request does not come from srvscripts.com, and we do not see what anyone checks.
What it looks like
$ srvs check example.com
check: example.com
DNS
✓ Name servers ns1.example.net, ns2.example.net
✓ Address 203.0.113.10 · IPv6 2001:db8::10
✓ DNSSEC signed and validated
HTTPS certificate
✓ Trusted yes, chain is valid
! Expires 2026-10-20 08:00 UTC (9 days left)
→ Renew soon; check that automatic renewal (AutoSSL, certbot, acme.sh) is working.
E-mail
✓ SPF v=spf1 include:_spf.google.com ~all
3 of 10 DNS lookups
! DMARC v=DMARC1; p=none; rua=mailto:dmarc@example.com
p=none only monitors: spoofed mail using this domain is still delivered.
...
21 passed · 2 warning(s) · 0 failed · 0 not checked
Example output for a made-up domain.
Commands
| Command | What it checks |
|---|---|
srvs check | Everything at once for a domain: name servers, addresses, DNSSEC, CAA, HTTPS certificate, HTTP to HTTPS redirect, security headers, MX, SPF, DMARC, DKIM, MTA-STS, TLS-RPT, BIMI and blacklists for the mail server IPs. Online: Email domain health check |
srvs dns | DNS records for a name (A, AAAA, CNAME, MX, NS, TXT, CAA and SOA by default, or the types you list); an IP gives its PTR. Online: DNS lookup |
srvs mail | MX and reverse DNS, SPF with the 10-lookup count, DMARC, DKIM, MTA-STS, TLS-RPT and BIMI for a domain. Online: SPF lookup counter, MTA-STS checker |
srvs ssl | Chain of trust, name match, expiry, key, protocol and cipher for a host and port; STARTTLS on ports 25, 587, 143 and 110. Online: SSL certificate checker |
srvs http | HTTP to HTTPS redirect, redirect chain, status, response time and six security headers for a URL or host. Online: Security headers checker |
srvs bl | 29 IP blacklists for an IP; for a domain, its mail server IPs plus Spamhaus DBL, SURBL and URIBL. Online: IP blacklist check |
Every command accepts several targets, for example srvs ssl mail.example.com:993 mail.example.com:587 example.com. Add --json for machine-readable output, -q to show only problems, and --resolver to choose the DNS server. By default srvs uses your system resolver: the nameserver lines of /etc/resolv.conf on Linux and macOS, and the DNS servers of your active network adapters on Windows (as shown by ipconfig /all). Only if none is found does it fall back to 1.1.1.1 and 8.8.8.8, and the output says so next to “Resolver:”.
Privacy
- Every check runs from your own machine. Nothing is sent to srvscripts.com, and there is no telemetry or update check.
- The program only contacts what you ask it to check: your DNS resolver, the websites and mail servers you name, and the blacklists for
srvs bl.
Use it in cron or monitoring
Exit codes: 0 every check that ran passed, 1 at least one warning or failure, 2 something could not be checked and nothing failed. A failure always wins over “could not check”, so a monitor never misses a real problem. With --ignore-warnings, warnings no longer count but nothing else changes: a failure is still 1 and a check that could not run is still 2. With --json, the exit field always equals the exit status.
# Mail me when a certificate is within 21 days of expiry, or when the mail setup breaks.
15 6 * * * srvs ssl example.com mail.example.com:587 --warn-days 21 -q --no-color || mail -s "srvs: TLS" you@example.com
30 6 * * * srvs mail example.com -q --no-color --ignore-warnings || mail -s "srvs: mail records" you@example.com
Good to know
- Blacklists and public resolvers. Spamhaus and URIBL refuse queries that arrive through public resolvers such as 1.1.1.1 or 8.8.8.8, and some resolvers answer “not listed” for everything.
srvschecks each list’s own test entry (RFC 5782) and reports not checked instead of clean when it does not come back. Use your own resolver or a free Spamhaus DQS key. - Port 25. Many home and cloud networks block outgoing port 25, so a check of port 25 shows not checked. Run it from a server, or check port 587 or 465.
- DKIM. A DKIM key can only be found with its selector.
srvstries the common ones; find yours in thes=part of theDKIM-Signatureheader and pass--selector.
Install
Linux and macOS: the script downloads the release for your system, checks its SHA-256 checksum and installs srvs to /usr/local/bin (or ~/.local/bin without root). Read it first if you like: it is short.
curl -fsSL https://raw.githubusercontent.com/srvscripts/srvs-cli/main/scripts/install.sh | sh
Windows (PowerShell):
irm https://raw.githubusercontent.com/srvscripts/srvs-cli/main/scripts/install.ps1 | iex
By hand: download the archive for your system from GitHub Releases (Linux, macOS and Windows, each for amd64 and arm64), check it against SHA256SUMS and put srvs in your PATH. With Go: go install github.com/srvscripts/srvs-cli/cmd/srvs@latest (building needs Go 1.26 or later; Go 1.21 to 1.25 downloads it automatically unless GOTOOLCHAIN=local is set)
Then run srvs check yourdomain.com. To pin a version, set SRVS_VERSION=v0.1.1 before the install command.
Questions or a wrong result? Contact us. Security problems: see how to report them.
