Set up HTTP monitoring: keep an eye o...
24 Jun 2026
Set up HTTP monitoring: keep an eye on your website
A website can exist technically yet still not function properly for your visitors. With HTTP monitoring you regularly check whether a specific URL is accessible, which HTTP status code the web server returns and how quickly the page responds. This lets you detect outages, error messages or unusually long load times at an early stage, before they remain unnoticed for an extended period. In this article you will learn exactly what HTTP monitoring is, which errors you can uncover with it and how to set up the monitoring step by step with Hosttest Plus.
Author:
Christopher | 24 Jun 2026
Christopher | 24 Jun 2026
via Gemini
In a Nutshell
HTTP monitoring automatically checks the availability, HTTP status codes and response times of URLs and provides the central basis for proactive website monitoring. It detects outages, faulty redirects and performance degradations and should be combined with SSL, DNS and port checks.
- Core checks: Regular HTTP/HTTPS probes (status code, response time, redirect chain), keyword checks for content validation and SSL certificate monitoring; for shops/SaaS, API and checkout endpoints should be checked separately.
- Check intervals & alerting: Choose intervals according to criticality (1 min for shop/critical, ~5 min for corporate sites, 10–15 min for static projects); configure alerts across multiple channels with repeat checks for verification.
- Error analysis & limitations: Uncover HTTP errors (4xx/5xx), 502/504 or long response times; further narrow down causes using ping, DNS lookup, port checks, load balancer/backend logs, since synthetic HTTP checks do not fully capture client‑side or asset‑specific issues.
- We’ll show you how to set it up within a few minutes with hosttest Plus.
Website monitoring
HTTP Monitoring: Detect website outages early
A website can appear technically reachable and still not work properly for visitors. HTTP Monitoring regularly checks whether your URL is actually reachable, which status code the web server returns and whether the response time is within the expected range.
🔎
Reachable doesn't necessarily mean it's working properly
A functioning website is a vital foundation for businesses, online shops and sole traders. It informs potential customers, accepts orders, generates enquiries or provides digital applications. Technical faults can therefore have noticeable consequences within a short time.
It is not enough to simply assume that the web server is generally running and that the domain is correctly registered. A website can still be faulty or not served at all despite active web hosting and a reachable server.
Basics
What is HTTP monitoring?
HTTP monitoring automatically requests a specified internet address at regular intervals. The monitoring system sends a request to the relevant web server and analyses its response.
Check availability
The monitoring checks whether the specified URL is reachable and whether the web server responds to the request at all.
Evaluate status codes
The HTTP status code indicates whether the page was delivered successfully, redirects, or returns an error.
Measure response time
Additionally, it can measure how long the server takes to respond to the request.
Check redirects
HTTP monitoring can detect whether redirects are functioning and whether the final intended page is reached.
Verify content
Advanced checks can verify whether the delivered page contains an expected term or content.
HTTP and HTTPS
HTTP monitoring works for unencrypted HTTP connections and encrypted HTTPS connections. Certificate validity should additionally be monitored via SSL monitoring.
Benefits
Why is HTTP monitoring important?
Website owners do not necessarily notice an outage immediately. Without monitoring, an issue is often only noticed when customers, employees or business partners point it out.
Without monitoring
- Visitors may be unable to use the website.
- Products, shopping carts or checkout processes in an online shop may not function correctly.
- Contact enquiries, bookings or leads do not come through.
- Advertising campaigns continue to send visitors to faulty landing pages.
- Trust in the company can suffer.
With HTTP monitoring
- Issues are detected more quickly.
- Erroneous status codes or redirects become visible.
- Unusually long response times are detected early.
- Important subpages can be monitored selectively.
- The time between outage and response is significantly reduced.
Common issues
What issues does HTTP monitoring detect?
HTTP monitoring reveals complete outages, faulty responses, broken redirects and unusually long response times.
01
The website is completely inaccessible
If the web server does not respond to the request, this can indicate a server outage, a network disruption, maintenance, overload or exhausted hosting resources.
- Server or hardware failure
- Network outage
- faulty web server configuration
- overload due to too many requests
- crashed web server service
02
The web server returns an incorrect status code
Every HTTP request is answered with a status code. This indicates whether the request was processed successfully or whether an error occurred. A normal website will usually return status code 200. For a permanently configured redirect, a 301 status code can be correct.
03
Redirects do not work correctly
Redirects are used after domain changes, URL structure changes or when switching from HTTP to HTTPS. Errors can cause visitors to land on the wrong page or become stuck in a redirection loop.
- redirect points to a non-existent page
- destination address contains a typo
- HTTP is not correctly redirected to HTTPS
- www and non-www versions incorrectly point to each other
- an endless redirection loop occurs
04
Response times increase significantly
A website does not have to fail completely to become practically unusable for visitors. If the response time increases significantly, visitors wait longer for the page to begin loading.
- high server load
- slow or overloaded database
- faulty plugins or extensions
- complex PHP processes
- slow external interfaces
- exhausted CPU or memory resources
The measured HTTP response time is not the same as the full load time of a website. However, it provides an important indication of how quickly the web server generally responds to a request.
Status codes
Key HTTP status codes at a glance
Which status code is considered correct depends on the monitored URL. Monitoring should therefore be configured to take the expected response into account.
| Status code | Meaning | Monitoring relevance |
|---|---|---|
| 200 OK | The requested page was served successfully. | For normal websites usually the expected state. |
| 301 / 302 | The request is redirected to another URL. | Can be correct when a redirect has been intentionally configured. |
| 403 Forbidden | Access to the resource was denied. | For public pages typically an indication of an issue. |
| 404 Not Found | The requested page was not found. | Critical for important subpages, e.g. after site relaunches or URL changes. |
| 500 Internal Server Error | An internal server error occurred. | Often critical, as the application cannot process the request correctly. |
| 502 Bad Gateway | An upstream server or proxy received an invalid response. | May indicate problems with a proxy, load balancer or backend system. |
| 503 Service Unavailable | The service is temporarily unavailable. | Typical during high load, maintenance or when the application is unreachable. |
| 504 Gateway Timeout | An upstream service did not receive a response in time. | May indicate slow backends, databases or external services. |
Process
How does HTTP monitoring work?
HTTP monitoring runs automatically in the background. The website owner specifies which URL should be checked and at what interval the check should be performed.
1
URL is accessed
The monitoring system automatically accesses the specified URL.
2
Request reaches the web server
The request is sent over the Internet to the appropriate web server.
3
Response is analysed
The HTTP status code, response time and optionally the delivered content are checked.
4
Error is confirmed
A repeat check can help distinguish short-term network issues or individual timeouts from genuine outages.
5
Notification is triggered
If the error persists, a notification is triggered so the cause can be investigated and resolved promptly.
Practical
Which pages should be monitored?
Many website owners initially monitor only the homepage. It is a sensible starting point, but does not always reflect the entire website.
Homepage
The most important basic check for the general availability of your website.
Landing pages
Particularly important when advertising campaigns or SEO traffic direct users to specific pages.
Product pages
For shops, central category and product pages should be checked regularly.
Checkout
Cart and ordering processes are especially business-critical for online shops.
Contact pages
Contact forms and enquiry areas should not only be reachable but also delivered correctly.
Login areas
Customer areas, member areas and portals should be monitored separately.
API endpoints
Publicly accessible APIs, webhooks or status pages can also be checked via URL.
Revenue-critical pages
Particularly important subpages should have separate checks instead of being covered only via the homepage.
Interval
How often should a website be checked?
The appropriate check interval depends on how important the website is and what consequences an outage may have. The shorter the interval, the faster an issue will be detected.
Private website or small project
For simple information sites, blogs or hobby projects, an interval of about 10 to 15 minutes is often sufficient.
Company website
For corporate websites, important landing pages and contact pages, an interval of around 5 minutes is often sensible.
Online shop
For shops, booking systems or lead pages, even a short outage can have direct financial consequences. Checks every minute or every few minutes are recommended here.
Business-critical application
Customer portals, SaaS applications, APIs or central business processes should be monitored particularly closely.
Context
Limitations of HTTP monitoring
HTTP monitoring shows whether a specific URL is reachable and what response the web server returns. However, the check cannot automatically determine every technical cause of an error.
Possible causes of errors
- DNS issues
- expired or misconfigured SSL/TLS certificate
- network outage
- web server error
- database issues
- CMS, plugin or theme errors
- external interfaces
- exhausted hosting resources
What HTTP monitoring does not fully detect
A page can return status code 200 even though individual images, JavaScript functions, forms or external components do not work correctly. HTTP monitoring should therefore be understood as a central baseline check and, if necessary, combined with additional types of monitoring.
Combination
Combine HTTP monitoring with other checks
The different types of monitoring provided by website monitoring tools check different layers of the technical infrastructure. Only by combining them can an issue be narrowed down more precisely.
Ping Monitoring
Checks whether a server or network device is generally reachable over the network. A successful ping response, however, does not necessarily mean that the web server is functioning.
Port Monitoring
Checks whether a specific network port is reachable. For websites, ports 80 (HTTP) and 443 (HTTPS) are particularly relevant.
Keyword Monitoring
Checks the content of the delivered web page. This makes it possible to determine whether the expected content is actually displayed despite a 200 status code.
SSL Monitoring
Monitors the certificate required for HTTPS and can warn of an impending expiry or a misconfigured certificate.
DNS Monitoring
Checks whether a domain resolves correctly and points to the intended destination. Incorrect DNS records can make a website unreachable.
Better root-cause analysis
If the server is reachable by ping while the HTTP check fails, the problem may lie with the web server or the application. If the DNS check already fails, the domain configuration should be checked first.
HOSTtest Plus
HTTP Monitoring with HOSTtest Plus
With HOSTtest Plus, websites and other online services can be monitored centrally. For HTTP monitoring a chosen URL is entered, which is then checked automatically at regular intervals.
This can monitor whether the website is reachable, which status code it returns and how quickly the server responds to the request. If an error occurs, website operators receive a notification and can promptly begin investigating the cause.
HTTP Monitoring
Checks the availability, status code and response time of a URL.
Keyword Monitoring
Verifies that the expected content is being delivered.
SSL Monitoring
Alerts about certificate issues and upcoming expiries.
DNS Monitoring
Monitors whether domains resolve correctly.
Ping Monitoring
Checks basic network reachability.
Port Monitoring
Monitors critical services and network ports.
Step by step
How to use HOSTtest Plus as an HTTP monitoring tool
An HTTP monitor can be set up quickly in HOSTtest Plus. After logging in, create a new monitor, choose the appropriate monitoring type and then specify which URL should be checked and at what interval.
1
Create an account or log in
First create a free HOSTtest Plus account or log in with your existing credentials.
2
Create a new monitor
Open the menu section Pulse → Monitors. There you can create an individual monitor for your website or a specific subpage.
Screenshot: Create a new HTTP monitor in HOSTtest Plus
3
Select HTTP as the monitor type
Select HTTP as the monitor type. This makes HOSTtest Plus check whether the specified URL is reachable and how the web server responds to the request.
4
Set the URL and check interval
Enter the URL to be monitored and then choose the desired check interval. The more important the website or subpage, the shorter the interval should be.
5
Configure notifications
Decide how you want to be notified in the event of an outage or an erroneous response. This lets you react quickly if your website is not reachable as expected.
6
Activate HTTP monitoring
Activate HTTP monitoring by clicking "Create monitor". From that moment HOSTtest Plus will automatically check your URL at the specified interval.
Screenshot: Status and analysis of your HTTP monitor
✅
Conclusion: HTTP monitoring as the foundation of website monitoring
HTTP monitoring is one of the most important foundations of reliable website monitoring. It regularly checks whether a URL is reachable, which status code the web server returns and how quickly it responds to requests.
This not only makes complete outages visible. Faulty redirects, internal server errors, unreachable subpages and unusually long response times can also be detected early. When combined with a keyword check, it is additionally possible to verify whether the expected content is actually being delivered.
Especially for corporate websites, online shops and business-critical applications, a rapid notification can significantly shorten the duration of an outage. HTTP monitoring shows, from the perspective of an external system, whether visitors are actually able to reach the desired page, and thus forms the most important basis for comprehensive website monitoring.
Write a comment
- Monitoring
Tags for this article
More web hosts
More interesting articles
Website Monitoring: The tools for monitoring your online presence, compared
This article provides a comprehensive overview of website monitoring and presents the best tools for monitoring a websit...
Monitor websites for free: A comparison of free website monitoring tools
In this article we look at the best-known free website monitoring tools and compare which features they offer in their f...
HOSTtest Plus: Free Website Monitoring for Webmasters, Agencies, and Businesses
Websites must be accessible at all times today. Just a few minutes of downtime can cost visitors, enquiries, and revenue...
Media Partner:
