Switching from UptimeRobot? Import your monitors in one click with a read-only API key.Start free →
  1. Home
  2. Tools
Free tools

Free tools for the questions that come up mid-incident

No account, no card. Paste a hostname or a number and get an answer.

Why these tools exist

Most of what an on-call person types at the start of an incident is a handful of small lookups. Is the site down for everyone or just for me? When does that certificate expire? What does the MX record say right now? What does the cache header on this response look like? We built these utilities for ourselves while running monitors, and we left them open because they are useful whether or not you ever become a customer.

The tools that touch a live target, such as the response-time test and the site status check, send real requests from our checkers in two regions, so the answer is not coloured by your own network or resolver cache. The calculators (uptime, cron, subnet) run in the page and send nothing anywhere. The DNS tools query public resolvers and show what a recursive lookup returns, with a note on what the same query would look like in dig on your own terminal.

Every tool is rate limited a little, which keeps it free for everyone and keeps it from being used to probe targets. If you find yourself running the same lookup daily, that is the signal to turn it into a monitor: a DNS monitor will tell you when a record changes, an SSL monitor will warn at 30, 14 and 7 days, and a domain monitor will watch the registration clock. The monitoring types overview lists them all.

All tools by category

25 pages in 5 groups. Search by name, record type or what you are trying to find out.

Is it up, and how fast?

Live requests from our checker regions.

Certificates, headers and domains

The quiet clocks and settings that take sites down.

DNS records

One page per record type, queried over DNS-over-HTTPS from your browser.

Email authentication

SPF, DKIM and DMARC: why mail lands in spam or gets rejected.

Calculators and builders

Run in your page, send nothing anywhere.

From a one-off lookup to a monitor

A lookup answers the question once. The cases below are where a repeating check saves you the next lookup. See SSL monitoring after the certificate checker, DNS monitoring after a record lookup, domain expiry monitoring after the domain tool, and cron monitoring after the cron builder. If you are comparing vendors rather than debugging, the comparison hub is the better stop, and developers wiring monitoring into scripts will find the REST API more useful than any web form.

Turn the check you keep repeating into a monitor

Free plan, 30 monitors, no card. Paste the URL you were just testing.