Open source · self-hosted · no telemetry

Watches your domains. Emails you when something breaks.

network-tools is a self-hosted domain monitor. It checks DNS, email authentication and TLS for all your domains on a schedule, keeps a history of every run, and sends an email only when something really changes.

  • 14 checks
  • 5 min scheduler
  • 0 passwords

Made for people who run domains

Email deliverability and HTTPS break quietly: an SPF record crosses the 10-lookup limit, a DKIM key disappears after a provider change, a certificate is not renewed, a domain expires. network-tools notices before your users do.

Alerts on real changes

A mail goes out when a check gets worse, a problem is fixed, or records change – not on every run. Timeouts and resolver hiccups never cause false alarms.

Full history

Every check run is stored with all details, so you can see what a record looked like last week and when it changed. Old runs are pruned automatically.

Built for many domains

Group domains by customer, inherit DKIM providers, set intervals per domain and send alerts to global, customer and domain recipients. Ideal for agencies and IT service providers.

Configured in the browser

SMTP, recipients, thresholds, resolvers and the Spamhaus DQS key live in the backend. Secrets are encrypted in the database.

Passkeys, no passwords

Log in with a passkey, or with a one-time magic link that is valid for 15 minutes. There are no passwords to leak.

Your server, your data

Runs as a Docker image on your own server. It only contacts the resolvers, registries, blacklists and hosts the checks need.

14 checks per domain

Each check returns OK, info, warning, error or “not checkable”. Individual checks can be switched off per domain.

MX
Records, null MX (RFC 7505), A/AAAA of the MX hosts, MX pointing to an IP or a CNAME.
A / AAAA
Domain and www. or your own web hosts, missing IPv6, private or reserved addresses.
PTR / reverse DNS
PTR records of MX and outgoing mail server IPs, forward-confirmed reverse DNS (FCrDNS).
SPF
Duplicate records, +all and ?all, a recursive counter for the 10-DNS-lookup limit including redirect, void lookups.
DKIM
Known selectors for Microsoft 365, Google Workspace, Mailchimp, SendGrid, Mailjet, Brevo, HubSpot, Zoho, Mailgun and IONOS, plus custom selectors; RSA key length.
DMARC
Policy, sp, pct, aggregate reports and the authorization record for external report receivers.
MTA-STS
TXT record, policy fetched over HTTPS, mode, max_age and whether every MX host is covered.
TLS-RPT
Record and report targets; a warning if MTA-STS is active without TLS reporting.
BIMI
Record, SVG Tiny PS logo and size, DMARC enforcement requirement, VMC/CMC certificate.
DNSSEC
DS at the registrar, DNSKEY in the zone, validation via the AD flag, SERVFAIL on bogus signatures, deprecated algorithms.
TLS certificate (HTTPS)
Trust, host name and expiry for the domain, www. and mta-sts.; outdated TLS versions.
TLS certificate (SMTP)
Optional STARTTLS on port 25 of every MX host: availability, trust, host name, expiry.
Domain expiry
Registration expiry and status via RDAP (IANA bootstrap), transfer lock.
Blacklists
MX and outgoing IPs and the domain against free RBLs such as SpamCop, PSBL, Mailspike, UCEPROTECT, SURBL and URIBL; Spamhaus ZEN and DBL only via DQS with your own key.

Every rule in detail: Checks in the wiki.

Alerts you can trust

After every run, each check is compared with the previous run of the same domain.

  • Worse – e.g. OK → warning, or a new blacklist listing.
  • Fixed – a warning or error is gone (can be turned off).
  • Configuration changed – same status, different records: a new SPF include, another certificate, a changed DMARC policy.
  • Never for timeouts or resolver problems, and only logged for IP changes of CDNs and Microsoft 365 unless you opt in.

Details: Notifications in the wiki.

Install in five steps

network-tools ships as a Docker image (ghcr.io/roberteinsle/network-tools) with a PostgreSQL database. The included Compose file is made for Coolify but runs on any Docker host.

  1. Database. Create a PostgreSQL database in Coolify and enable backups.
  2. App. Create a Docker Compose (Empty) resource with deploy/docker-compose.coolify.yml and set APP_KEY, APP_URL and the DB_* variables.
  3. Domain. Add your domain with port 8080 to the app service and deploy. Web app, queue worker and scheduler start from the same image.
  4. First login. Run php artisan app:user you@example.com in the container. It prints a login link, so no SMTP is needed yet.
  5. Set up. Register a passkey, enter your SMTP server and alert recipients, then add your domains.

Step by step, including updates and local development: Installation guide · Configuration

Frequently asked questions

What does network-tools check?

MX, A/AAAA, PTR with forward-confirmed reverse DNS, SPF including the 10-DNS-lookup limit and void lookups, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI, DNSSEC, TLS certificates for HTTPS and SMTP STARTTLS, domain expiry via RDAP, and DNS blacklists.

When does it send an email?

When a check gets worse, a problem is fixed, or the configuration changes, for example a new SPF record or another certificate. Timeouts and resolver problems never trigger an alert.

Does it query Spamhaus?

Only through the Spamhaus Data Query Service (DQS) with your own key. The public Spamhaus zones are never queried and cannot be added.

Why are some blacklists “not checkable”?

Many RBLs refuse queries from public resolvers such as 8.8.8.8. Run your own resolver (for example Unbound) and enter it in the settings.

How often are domains checked?

Per domain: hourly, every 3, 6 or 12 hours, or daily. A scheduler queues due domains every five minutes, and you can start a check at any time.

Is it free?

Yes. The source code is on GitHub, and it runs on your own server without license costs or telemetry. The backend interface is currently in German.