Website monitoring, API monitoring,
server monitoring — and more.
Seven purpose-built monitor types covering website uptime monitoring, API monitoring, server and port monitoring, silent failure detection, SSL certificate expiry, multi-step Journey monitoring, and Sitemap Link monitoring. Deep Monitoring — free to start.
HTTP / HTTPS Monitor
The foundation of website monitoring and API monitoring.
The most common monitor type and the core of any website monitoring setup. MonitorGiant makes an HTTP or HTTPS request to any URL and checks whether it returns an expected status code. Use it for website monitoring, API monitoring, health-check endpoints, and any URL your stack depends on. The free plan uses HEAD method. GET and POST with custom headers and request bodies are available on paid plans.
Use it for:
Monitor your checkout API endpoint every 5 minutes on the free plan. Alert if status is not 200. Upgrade to a paid plan for 30-second checks and POST requests with custom headers.
Configuration
- URL (any HTTP or HTTPS endpoint)
- HTTP method: HEAD (free) · GET/POST (paid plans)
- Custom headers (paid plans)
- Custom request body for POST (paid plans)
- Accepted status codes (e.g. 200, 201, 204)
- Check interval (5 min free · 30 sec paid)
Keyword Detection Monitor
Catch the failures that status codes miss.
Goes one step further than an HTTP check — it fetches the full response body and searches for a specific keyword or phrase. You can configure the monitor to alert when the keyword is absent (proving the page loaded correctly) or when it is present (detecting error messages). A 200 OK response that contains "Error: database unavailable" is worse than a 503 — because it looks fine from the outside.
Use it for:
Check your checkout page for "Add to Cart" every 5 minutes. If the keyword is absent, the cart feature has failed — alert before customers notice.
Configuration
- URL to fetch (GET method)
- Keyword or phrase to search for
- Alert mode: present (error detection) or absent (content verification)
- Check interval (5 min free · 30 sec paid)
Ping / Reachability Monitor
Server monitoring at the network level.
The simplest form of server monitoring — checks whether a host is reachable on the network by attempting a TCP connection on port 80. A host is counted as reachable if the port is open or the connection is actively refused, confirming the server exists and is responding. Designed to work on all cloud environments, including those that restrict raw ICMP ping.
Use it for:
Monitor your database server by hostname every minute. Alert if unreachable. Spot network-level issues independently of your HTTP checks.
Port Monitor
Deep server monitoring — confirm the service is actually listening.
Server monitoring at the service level: attempts a TCP connection to a specific port and verifies it is accepted within the configured timeout. Works for any TCP service — databases, mail servers, game servers, custom application ports. This goes further than a simple ping check: a server can be reachable but have a crashed database that is no longer accepting connections on port 5432.
Use it for:
Monitor your Redis cache on port 6379 every 5 minutes. A connection failure here predicts application slowdowns before users experience them.
Configuration
- Hostname or IP address
- Port number (1–65535)
- Connection timeout
- Check interval
SSL Certificate Expiry Monitor
Never let a lapsed certificate take your site offline.
Connects to a host over TLS, reads the SSL certificate, and reports how many days remain before it expires. The platform alerts your team a configurable number of days before expiry (default: 15 days), giving you ample time to renew. The monitor also flags immediately if a certificate is already expired. Certificate expiry is one of the most common — and most embarrassing — causes of unplanned downtime. Available on paid plans.
Use it for:
Set an SSL monitor for every client domain. Alert 30, 15, and 7 days before expiry. Never have a site go down because a certificate renewal failed silently.
Configuration
- Domain or hostname to check
- Alert threshold in days (default: 15 days)
- Check interval
Journey Monitor
Your checkout is one broken step away from zero revenue.
A Journey monitor walks through a sequence of HTTP requests in order — exactly as a real user navigates your site. Each step has its own URL, expected status code, and optional keyword check. MonitorGiant runs all steps in order, stops at the first failure, and tells you exactly which step broke and why. A standard HTTP monitor reports your site as UP even if your checkout page returns a blank screen. A Journey monitor catches it. Available on paid plans.
Use it for:
E-commerce: Homepage → Product page → Cart → Checkout → Place order. Step 4 (Checkout) fails — you get an alert naming exactly that step, not just "site is down." Catch revenue-killing breakages before a single customer notices.
Configuration
- Up to 10 steps per journey — each with URL, expected status code, optional keyword
- Session cookie carried between steps for authenticated flows
- Per-step keyword present / absent validation
- Configurable check interval
- Step-by-step waterfall view in the results dashboard
- 3 one-click templates: E-commerce checkout · SaaS sign-up · API sequence
Sitemap Link Monitor
You have broken links. Google already knows. Do you?
A Sitemap Link Monitor reads your sitemap.xml and checks every listed URL on a schedule using lightweight HTTP HEAD requests — no full page load, no server overhead. Broken links (4xx), server errors (5xx), and redirect chains are detected and reported as one consolidated alert per scan. Scan diff tracks which URLs appeared or disappeared since the last run. Available on paid plans.
Use it for:
Your sitemap has 248 URLs. A CMS plugin update silently unpublishes 3 product pages (404). MonitorGiant's next scheduled scan catches all three, sends one alert listing each broken URL, and logs the diff. You fix them before Google's next crawl and before a single customer hits a dead page.
Configuration
- Automatic sitemap discovery — finds sitemap.xml, sitemap_index.xml, nested sitemaps
- HTTP HEAD requests only — zero page-load overhead on your server
- Configurable scan frequency: daily, every 6h, every 2h, or hourly
- Consolidated alert per scan — one summary, not one alert per broken URL
- Scan diff — alerts when URLs are added or removed from the sitemap
- Full scan history with per-URL response time tracking
Website monitoring, API monitoring & server monitoring — one platform.
HTTP, Keyword, Ping, Port, SSL, and Journey monitoring — six monitor types in one Deep Monitoring platform. Instant downtime alerts. Free uptime monitoring to start.
Get started free →