Get instantly notified when your website goes down
SMS Call Email
Start monitoring free
  1. Homepage
  2. Expert articles about web hosting
  3. Set up HTTP monitoring: Keep an eye on your website
Contents

Set up HTTP monitoring: Keep an eye on your website

A website can exist technically and still not function correctly for your visitors. With HTTP monitoring you regularly check whether a specific URL is accessible, which status code the web server returns and how quickly the site responds. This lets you recognise 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 Christopher   | 24 Jun 2026
Set up HTTP monitoring: Keep an eye on your website

via Gemini

    In a Nutshell

    HTTP monitoring automatically checks the availability, HTTP status codes and response times of URLs and forms 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 shops/critical, ~5 min for company websites, 10–15 min for static projects); configure alerts across multiple channels with repeat checks for verification.
    • Error analysis & limitations: Reveal HTTP errors (4xx/5xx), 502/504 or long response times; further narrow down causes using ping, DNS lookup, port checks, load‑balancer/backend logs, as synthetic HTTP checks do not fully capture client‑side or asset‑specific issues.
    • We’ll show you how to set it up with hosttest Plus within a few minutes. 
    Website Monitoring

    HTTP Monitoring: Detect website outages early

    A website can appear to be technically reachable and still not function correctly 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 does not necessarily mean functional

    A functioning website is a crucial foundation for businesses, online shops and the self-employed. 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 the Domain is correctly registered. A website can be faulty or not delivered at all despite active web hosting and a reachable server.

    Fundamentals

    What is HTTP Monitoring?

    HTTP monitoring automatically requests a specified internet address at regular intervals. The monitoring system sends a request to the responsible web server and evaluates its response.

    Check availability

    The monitoring checks whether the specified URL is reachable and whether the web server responds to the request.

    Evaluate status codes

    The HTTP status code indicates whether the page was served successfully, redirected or returned 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 work and whether the final target page is reached.

    Check 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 operators do not necessarily notice an outage immediately. Without monitoring, a fault often only becomes apparent when customers, employees or business partners point it out.

    Without monitoring

    • Visitors may not be able to use the website.
    • Products, shopping carts or checkout processes in an online shop may not work.
    • Contact enquiries, bookings or leads do not come in.
    • Advertising campaigns may direct visitors to faulty landing pages.
    • Trust in the company can suffer.

    With HTTP monitoring

    • Incidents are detected more quickly.
    • Faulty status codes or redirects become visible.
    • Unusually long response times are noticed early.
    • Important subpages can be monitored selectively.
    • The time between outage and response is significantly reduced.
    Typical issues

    What problems 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 failure of the server, a network outage, 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 an error occurred. On a normal website, a 200 status code is usually expected. For a permanently configured redirect, a 301 status code can, however, be correct.

    03

    Redirects are not functioning correctly

    Redirects are used after domain changes, URL structure adjustments or when moving from HTTP to HTTPS. Errors can cause visitors to land on the wrong page or become stuck in a redirect loop.

    • redirect leads to a non-existent page
    • target address contains a typo
    • HTTP is not correctly redirected to HTTPS
    • www and non-www versions incorrectly point to each other
    • an infinite redirect loop occurs
    04

    Response times increase significantly

    A website does not need to fail completely to become practically unusable for visitors. If the response time increases significantly, visitors wait longer for the page to start 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 page load time of a website. However, it provides an important indication of how quickly the web server generally responds to a request.

    Status codes

    Important HTTP status codes at a glance

    Which status code is considered correct depends on the monitored URL. Monitoring should therefore be configured to account for the expected response.

    Status code Meaning Monitoring implications
    200 OK The requested page was served successfully. Typically the expected state for standard websites.
    301 / 302 The request is redirected to another URL. Can be correct if a redirect has been intentionally configured.
    403 Forbidden Access to the resource was denied. Usually indicates a problem for public pages.
    404 Not Found The requested page was not found. Critical for important subpages, e.g. after relaunches or URL changes.
    500 Internal Server Error An internal error occurred on the server. Often critical, as the application cannot process the request correctly.
    502 Bad Gateway An upstream server or proxy received an invalid response. May indicate issues with a proxy, load balancer, or backend systems.
    503 Service Unavailable The service is temporarily unavailable. Typical during overload, maintenance, or when the application is unreachable.
    504 Gateway Timeout An upstream service did not receive a response in time. May point to 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 requested

    The monitoring system automatically requests the specified web address.

    2

    Request reaches the web server

    The request is sent over the Internet to the relevant web server.

    3

    Response is analysed

    Status code, response time and, optionally, the delivered content are checked.

    4

    Issue is confirmed

    A repeat check can help distinguish short-term network problems or individual timeouts from genuine outages.

    5

    Notification is triggered

    If the issue persists, a notification is sent so the cause can be investigated and resolved promptly.

    In practice

    Which pages should be monitored?

    Many website operators initially monitor only the homepage. This 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

    Especially important when advertising campaigns or SEO traffic lead to specific pages.

    Product pages

    For shops, key category and product pages should be checked regularly.

    Checkout

    Shopping cart and checkout process are particularly business-critical for online shops.

    Contact pages

    Contact forms and enquiry areas should not only be reachable but also function 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 their own checks rather than being covered only by 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 might have. The shorter the interval, the sooner an issue is detected.

    Personal website or small project

    For simple informational websites, blogs or hobby projects, an interval of around 10 to 15 minutes is often sufficient.

    Business website

    For company websites, important landing pages and contact pages, an interval of around 5 minutes is often advisable.

    Online shop

    For shops, booking systems or lead pages, even a short outage can have direct financial consequences. Here checks every minute or every few minutes are recommended.

    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 identify every technical cause of an error.

    Possible causes of errors

    • DNS issues
    • expired or misconfigured SSL/TLS certificate
    • network outage
    • web server errors
    • database issues
    • CMS, plugin or theme errors
    • external interfaces
    • exhausted hosting resources

    What HTTP monitoring does not fully detect

    A page can return a 200 status code even though individual images, JavaScript functions, forms or external components are not functioning correctly. Therefore, HTTP monitoring should be regarded as a core baseline check and, where necessary, combined with other 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 a fault 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 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 allows you to see whether the expected content is actually displayed despite an HTTP 200 status code.

    SSL monitoring

    Monitors the certificate required for HTTPS and can warn of an impending expiry or a faulty certificate configuration.

    DNS monitoring

    Checks whether a domain is correctly resolved and points to the intended destination. Incorrect DNS records can make a website unreachable.

    Improved root cause analysis

    If the server is reachable by ping while the HTTP check fails, the problem may be 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 target URL is saved and 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 owners receive a notification and can promptly begin root-cause analysis.

    HTTP monitoring

    Checks availability, status code and response time of a URL.

    Keyword monitoring

    Verifies that the expected content is delivered.

    SSL monitoring

    Warns of certificate issues and upcoming expiries.

    DNS monitoring

    Monitors whether domains are resolving correctly.

    Ping monitoring

    Checks basic network reachability.

    Port monitoring

    Monitors key services and network ports.

    Try HOSTtest Plus for free
    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 at which 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 a customised monitor for your website or a specific subpage.

    Screenshot: Creating a new HTTP monitor in HOSTtest Plus

    http-monitor-anlegen-hosttestplus

    3

    Select HTTP as the monitor type

    Choose HTTP as the monitor type. HOSTtest Plus will then check whether the specified URL is reachable and how the web server responds to the request.

    4

    Specify 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

    Specify how you would like to be notified in the event of an outage or an erroneous response. This allows you to react quickly if your website is not reachable as expected.

    6

    Activate HTTP monitoring

    Switch the HTTP monitoring live by clicking “Create monitor”. From that point, HOSTtest Plus will automatically check your URL at the set interval.

    Screenshot: Status and analysis of your HTTP monitor

    http-monitor-ansehen-hosttestplus

    ✅

    Conclusion: HTTP monitoring as the basis of website monitoring

    HTTP monitoring is one of the most important fundamentals 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 reveals complete outages. Faulty redirects, internal server errors, unreachable subpages and unusually long response times can also be detected at an early stage. Combined with a keyword check, it can additionally verify that the expected content is actually being delivered.

    Especially for corporate websites, online shops and business-critical applications, a quick notification can significantly reduce the duration of an outage. From the perspective of an external system, HTTP monitoring shows whether visitors can actually reach the intended page, and thus forms the most important foundation for comprehensive website monitoring.

    Write a comment

    More web hosts

    More interesting articles

    Server Outage - Prevention and Immediate Measures

    A server outage is the worst possible news for a company. We show what can and should be done.

    Set up DNS monitoring: Keep an eye on your domain

    Faulty or outdated DNS records can cause your website to become unreachable, point to the wrong IP address, or result in...

    Website not reachable - Causes and Measures

    Anyone who operates their own website for a longer period of time will sooner or later be confronted with downtime. But ...

    Port Monitoring: How to monitor the services on your servers

    With port monitoring, you regularly check whether a specific network port is reachable and whether the service behind it...

    Keyword Monitoring: How to keep track of your content

    With Keyword Monitoring you regularly check whether important content is present on your website and identify incorrect ...

    Set up SSL monitoring: Keep track of your certificates

    An expired or incorrectly configured SSL certificate can cause visitors to see a security warning, make logins appear in...

    We have already helped hundreds of thousands of webmasters find the right hosting provider.