URL monitoring tools: know when an important URL fails
Dashboard demo · sample data
Sample values only: your website is not checked. Real measurements start after sign-up.
Connect to Search ConsoleThis is the real dashboard layout with sample values. Hover over a chart to see daily values.
Monitor this website for realShort answer
URL monitoring tools request a specific URL at fixed intervals, typically every one to five minutes, and check that it answers with the expected status code (usually 200), within an acceptable response time and, optionally, with the expected content. When a check fails and a retry confirms it, the tool alerts you. Monitor every URL that matters on its own, not just the homepage: login, checkout, API endpoints, landing pages. Domain name monitoring adds DNS, certificate and expiry checks for the domain itself. monitordefend checks each website’s URL every five minutes for uptime and response time and alerts by email.
- Status code, response time and content are the three core URL checks.
- Confirm failures with a retry to avoid false alarms.
- Monitor all business-critical URLs, not only the homepage.
A website is not one thing but a collection of URLs, and they do not fail together. The homepage may load perfectly while the login returns an error, the checkout times out or the API behind the mobile app is down. URL monitoring tools watch individual addresses and tell you which one has a problem. This page explains what a URL monitor checks, which status codes and response times are normal, how to pick the URLs worth monitoring, how URL monitoring relates to domain name monitoring, and what to look for when you compare URL monitoring tools.
What URL monitoring is
URL monitoring is the automated, repeated checking of a web address. A monitoring service sends an HTTP request to the URL from a server on the internet, measures how long the answer takes and evaluates it. If the answer is missing, too slow or wrong, the URL counts as down. The service records each result, so over time you also get an uptime percentage and a response time history per URL.
URL monitoring is the most common form of uptime monitoring. It is simple, it needs no access to your server and it reflects what visitors experience, because it uses the same public route to your site.
What a URL monitor checks
The basic check is the HTTP status code. Codes in the 200 range mean success; 300 codes are redirects, which a monitor usually follows; 400 codes are client errors such as 404 Not Found or 403 Forbidden; 500 codes are server errors such as 500, 502 Bad Gateway or 503 Service Unavailable. Most tools treat 4xx and 5xx answers and timeouts as down.
GET https://myshop.com/checkout DNS 18 ms · connect 22 ms · TLS 41 ms HTTP/2 200 OK · first byte after 386 ms Keyword "Place order" found Result: UP · response time 412 ms
Beyond the status code, URL monitors can check response time against a threshold, look for a keyword that must appear (or must not appear) in the page, validate redirects, check the SSL certificate and, for APIs, inspect JSON responses.
- Status code: is the answer 200, or an error?
- Response time: does the server answer fast enough?
- Content: does the page contain what it should?
- Redirects: does the URL end up where it should?
- Certificate: is HTTPS valid and not about to expire?
Which URLs to monitor
Start with the homepage, then add every URL whose failure costs money or trust even if the homepage works. For shops that is the cart and checkout, for SaaS products the login and the app, for lead generation the forms and landing pages of running campaigns, for developers the API health endpoints. Monitor the URL that is actually used, including the correct protocol and hostname, so that redirects and certificates are tested as well.
Avoid monitoring hundreds of minor URLs at short intervals. For large numbers of pages, a daily link crawl that finds broken pages is more efficient than individual uptime monitors.
Response time: what is normal?
Response time in URL monitoring usually means the time until the full HTML response has arrived, measured from the monitoring location. Under 500 milliseconds is good for most websites, under one second acceptable, several seconds a problem. Values depend on distance, hosting and caching, so compare a URL with its own history rather than with other sites.
Watch the trend. A slow increase over days often points to growing databases, exhausted resources or a failing cache; a sudden jump often follows a deployment or plugin update.
Check intervals and confirmation
Typical intervals range from 30 seconds to five minutes. Shorter intervals detect outages faster but cost more and produce more data. A five-minute interval means an outage is detected within five minutes plus the confirmation time, which is fine for most business websites.
Confirmation prevents false alarms. A single failed request can be caused by a brief network problem between the monitor and your server. Good URL monitoring tools retry immediately or check from a second location before raising an alert.
Domain name monitoring
Domain name monitoring watches the domain behind the URLs: DNS records, name servers, the certificate and the registration expiry date. A URL monitor notices when these fail, because the URL stops working, but only afterwards. Domain-level checks warn you before a certificate or registration expires and alert you when DNS records change unexpectedly. Combine both for important websites.
- Check: /checkout returns 502
- Retry after a few seconds: 502 again
- Incident opened, alert sent
- Check: 200 OK, incident closed
Alerts and incident history
When a URL goes down, the tool opens an incident and alerts you by email, SMS, push, chat or webhook, depending on the tool. When it recovers, you get an all-clear. The incident history with start, end and duration is the basis for uptime reports and for discussions with your hosting provider. Make sure alerts reach a shared inbox or channel, not a single person who may be on holiday.
Comparing URL monitoring tools
Most URL monitoring tools cover the basics. Differences show in intervals, the number of URLs per plan, confirmation logic, locations, alert channels, history and pricing. Free plans of tools such as UptimeRobot or StatusCake, and self-hosted Uptime Kuma, are a good start for a few URLs. Platforms such as Pingdom, Better Stack or Site24x7 add more locations, faster intervals and team features. Full website monitoring services combine URL checks with link, SEO and security monitoring.
- How many URLs and which interval are included?
- Are failures confirmed before alerting?
- Can you set response time thresholds per URL?
- Are keyword and redirect checks available?
- Which alert channels exist, and is history kept long enough?
Monitoring APIs and endpoints
APIs are URLs too, and often more critical than pages, because mobile apps, partners and internal services depend on them. Monitor a health endpoint that checks the database and important dependencies, not only a static response. Where possible, also check a real read request and validate the JSON body, for example that a field exists or a value is within range. Authentication tokens should be dedicated monitoring credentials with minimal rights.
Reading the uptime percentage
Uptime percentages look similar but mean very different amounts of downtime. 99 % allows about seven hours of downtime per month, 99.9 % about 43 minutes, 99.99 % about four minutes. When you compare a URL’s uptime with a hosting promise or a service level agreement, check how the provider counts: some exclude maintenance windows or only count outages longer than a few minutes.
Common mistakes
Monitoring only the homepage. Monitoring a URL that redirects elsewhere, so the actual page is never tested. Setting response time alerts so tight that they fire every day. Sending alerts to an inbox nobody reads. And never testing the alert path: point a monitor at a URL that returns an error once, to make sure the alert really arrives.
URL monitoring with monitordefend
monitordefend checks the URL of each website every five minutes from Germany, confirms failures with a second attempt and records uptime and response time, as the demo above shows. You set a response time threshold per site and receive email alerts. Beyond uptime, it can check the checkout URL, crawl for broken links and watch indexing and security signals. It does not offer multi-location checks, SMS or webhooks.
Frequently asked questions
What is URL monitoring?
The automated, repeated checking of a web address for availability, status code, response time and optionally content, with alerts when it fails.
What is the best interval for URL monitoring?
Five minutes is enough for most websites. Shops and APIs with strict availability targets often check every minute or more often.
Which HTTP status codes mean a URL is down?
Timeouts, connection errors and status codes in the 5xx range clearly mean down. Most tools also treat 4xx codes such as 404 or 403 as failures.
Should I monitor URLs that redirect?
Monitor the final URL visitors reach, and optionally the redirecting URL to make sure the redirect still works.
What is the difference between URL monitoring and domain name monitoring?
URL monitoring checks pages. Domain name monitoring checks the domain’s DNS records, certificate and registration expiry.
Can I monitor URLs for free?
Yes, several uptime monitors have free plans for a limited number of URLs at five-minute intervals, and the free status code checker on this site tests a URL once.
Related pages
Monitor your most important URLs
Start for free and set up your first check in minutes.
Start for free