Skip to content
Approvalens
TR

Monitoring · monthly subscriptions

Your sites and servers, watched around the clock.

Site monitoring checks your website from the outside, every five minutes. Server monitoring watches your Linux machines from the inside, every minute. One inbox, and an e‑mail only when something actually changes.

Monitor a siteMonitor a server
  • Sites from $4.99/month
  • Servers from $2.99/month
  • Cancel any time
Sample status board: two sites and two servers

SitesUptime, last 30 days

  • yoursite.comUp

    99.98% uptimeSSL 61 daysads.txt ✓

  • shop.yoursite.comCheck

    100% uptimeSSL 6 daysads.txt ✓

Servers

  • web-1CPU 7% · mem 63% · disk 71%OK
  • db-1disk 91% · full in ~2 daysCheck

Two products, one inbox

What do you want to watch?

Pick one, or both. They are separate subscriptions: a server doesn't need a website, and a website doesn't need a server.

For site owners and publishers

Site monitoring

from$4.99per month, 1 site

We check your site from the outside, the way a visitor, Google and AI crawlers see it.

  • Uptime every 5 minutes, an alert when it goes down and when it is back
  • SSL certificate expiry and validity
  • ads.txt and your publisher line
  • Googlebot and AdSense crawler access
  • 14 AI crawlers and llms.txt
  • Security headers, HTTPS and exposed /.env or /.git/

Includes one server

Monitor a siteWhat we check

For sysadmins and developers

Server monitoring

from$2.99per month, 1 server

A small open-source agent on your Linux server watches the machine itself. No website needed.

  • Disk and inodes, with a “full in N days” estimate
  • Memory, swap and load
  • An alert when the server or the agent goes silent
  • Security signals: miners, new ports, new SSH keys
  • Charts from 24 hours to 90 days
  • One-line install, MIT-licensed source

No website needed

Set up server monitoringRead the agent's source

Site monitoring

Seven things that quietly break a website

None of these show up on your own screen. A plugin rewrites robots.txt, a CDN starts challenging Googlebot, ads.txt disappears after a migration, the certificate runs out, a deploy leaves /.env readable. We check for them every day, and for uptime every five minutes.

  1. 1

    Uptimeevery 5 minutes

    We load your homepage. Two failures in a row (timeout or server error) open an incident; a bot challenge is not an outage (we show it on the site instead) and send one e‑mail; another goes out when the site is back, with how long it was down.

  2. 2

    ads.txtdaily

    We alert you if /ads.txt disappears, starts returning a web page, or loses the google.com line with your own publisher ID.

  3. 3

    Googlebot and the AdSense crawlerdaily

    We read robots.txt the way Google does and request your homepage as Googlebot and Mediapartners-Google, the crawler AdSense uses to read your pages.

  4. 4

    SSL certificatedaily

    A warning 14 days and again 7 days before the certificate expires, and straight away if it becomes invalid.

  5. 5

    14 AI crawlersdaily

    GPTBot, ClaudeBot, PerplexityBot and the rest: their robots.txt rules, a simulated request as each one, and your llms.txt.

  6. 6

    Security basicsdaily

    The http → https redirect, HSTS and three security headers (CSP, nosniff, a frame rule). And /.env or /.git/ becoming readable by anyone: that one is e‑mailed the same day.

  7. 7

    Weekly summaryweekly

    One e‑mail a week with each site's status, uptime and the changes of the week.

Start site monitoring

Server monitoring

The machine underneath, watched from the inside

Outside checks can't see a disk filling up or one process eating a whole core. The agent can: it reads the server every minute and tells you before your users notice.

Servers from $2.99/month

See server monitoringAgent & source code

  • Disk filling up

    A filesystem at 90%, or projected full within 48 hours at the rate of the last 6 hours. Inodes too.

  • Memory, swap and load

    Memory at 95% for 10 minutes, heavy swapping, processes killed for lack of memory, load above twice the cores for 15 minutes, a saturated disk, a failed service.

  • Server or agent silent

    No heartbeat for 15 minutes: the server is down, offline or the agent stopped.

  • Suspicious signals (heuristic)

    Crypto-miner names, programs running from /tmp or deleted, new listening ports, new crontab lines, new SSH keys, new setuid files, changed PHP or JS files. A reason to look, not an antivirus verdict.

Alerts

What lands in your inbox

Only what changed, with the evidence. No e‑mail when nothing changed, and no daily digest you learn to ignore.

Sample

Approvalens · Site monitoring

2 changes on yoursite.com

Since our previous check (6 Oct 2026, 09:30 UTC):

  • robots.txt now disallows Mediapartners-Google (AdSense) on the homepage (line 6: Disallow: /).
  • Cloudflare now returns 403 to GPTBot (simulated, seen on two daily checks in a row).
Simulated server answers must repeat on two daily checks before we write to you, so a single hiccup doesn't wake you up.
Sample

Approvalens · Server monitoring

db-1: disk / will be full in about 2 days

Detected 6 Oct 2026, 14:05 UTC:

  • Disk / is 91% full (184 of 202 GB).
  • It grew by about 380 MB an hour over the last 6 hours: at that rate it is full in about 2 days.
An e‑mail when a rule trips, with the numbers behind it. Fifteen minutes without a heartbeat is an alert too.

How to start

Running in a few minutes

Site monitoring

  1. 1Pick a plan size below, or enter one domain, and sign in with Google.
  2. 2Pay with Lemon Squeezy. Add your sites in your account; each is checked within minutes.
  3. 3Close the tab. We e‑mail you when something changes.
Monitor a site

Server monitoring

  1. 1Sign in with Google and pick a server plan.
  2. 2Add a server in your account: you get its install line with a one-time token.
  3. 3Run the line as root on the server. It reports within a minute.
Go to your servers

Pricing

Monthly plans, by size

Every plan has every check; you only choose how many sites or servers. Change the size any time from your account (the difference is prorated), cancel any time: monitoring runs to the end of the month you paid for.

Site monitoring

  • 1 site

    $4.99 per site

    $4.99per month

    Choose

  • 5 sites

    $4.00 per site · save 20%

    $19.99per month

    Choose

  • 10 sites

    $4.00 per site · save 20%

    $39.99per month

    Choose

  • 25 sites

    $2.80 per site · save 44%

    $69.99per month

    Choose

  • 50 sites

    $2.40 per site · save 52%

    $119.99per month

    Choose

Every site plan also includes one server agent.

Server monitoring

  • 1 server

    $2.99 per server

    $2.99per month

    Choose

  • 5 servers

    $2.40 per server · save 20%

    $11.99per month

    Choose

  • 10 servers

    $2.00 per server · save 33%

    $19.99per month

    Choose

  • 25 servers

    $1.60 per server · save 47%

    $39.99per month

    Choose

  • 50 servers

    $1.40 per server · save 53%

    $69.99per month

    Choose

No website needed. Already on a site plan? It includes one server.

  • Every check in every plan
  • Change size any time
  • Cancel any time
  • Secure payment by Lemon Squeezy

Or start with one site right now

Monitoring

Site monitoring

from$4.99per month

We watch the things that quietly break AdSense approval, AI visibility and security, and e-mail you only when one of them changes.

  • Uptime: your homepage loaded every 5 minutes, an e-mail when it goes down and when it is back
  • SSL certificate: a warning 14 and 7 days before it expires, and at once if it becomes invalid
  • ads.txt: an alert if it disappears or loses your google.com publisher line
  • Google access: robots.txt rules plus simulated homepage requests as Googlebot and Mediapartners-Google (AdSense)
  • 14 AI crawlers: robots.txt rules, simulated homepage requests and llms.txt, rechecked daily
  • Security: the http → https redirect, HSTS, security headers, and an alert at once if /.env or /.git/ becomes readable
  • Alerts only when something changes, with before and after, plus a weekly summary
What “simulated” means

Crawler requests come from our server with the crawler's user agent. A firewall that verifies crawlers by IP address can treat the real Googlebot or GPTBot differently, so a server-side change has to show on two daily checks in a row before we e-mail you. robots.txt, ads.txt, llms.txt and TLS changes are e-mailed the same day.

Plans by size, per month: 1 site $4.99 · 5 sites $19.99 · 10 sites $39.99 · 25 sites $69.99 · 50 sites $119.99.

Compare plans

Every full report already includes one month of this monitoring for its site.

Buying a full site report? It includes one month of site monitoring for that site.About the site report

Questions

What is the difference between site and server monitoring?

Site monitoring checks your website from the outside: is it up, is the certificate valid, can Google, AdSense and AI crawlers read it, is ads.txt in place, are the security basics right. Server monitoring puts a small agent on a Linux machine and watches the inside: disk, memory, load and security. They are separate plans; every site plan includes one server.

Do I need a website to monitor a server?

No. Server monitoring is its own plan, for 1 to 50 servers, and works on any Linux server with systemd: a database, a queue worker or a build machine is fine.

How is this different from a free uptime monitor?

Uptime is one of seven site checks. The others are things an uptime tool doesn't look at: ads.txt, Googlebot and the AdSense crawler's access, the certificate, AI crawlers and security basics like HSTS and an exposed /.env. And no outside tool can see a server's disk, memory or security settings.

Will you e‑mail me every day?

No. You get an e‑mail when something changes, when a site goes down and comes back, when a rule trips on a server, and one weekly site summary.

What does “simulated” mean?

Crawler requests go from our server with the crawler's user agent. A firewall that verifies crawlers by IP address may treat the real Googlebot or GPTBot differently, so a server-side change must show on two daily checks in a row before we e‑mail you. robots.txt, ads.txt and llms.txt changes are reported the same day.

Is monitoring included with the site report?

Yes: every full report includes one month of site monitoring for that site. Three days before it ends we send one reminder; to keep it running, add the site to a site plan.

How do I change or cancel?

From your account: Account → Plans and payments. A bigger or smaller plan applies at once (prorated); after cancelling, monitoring runs to the end of the month you paid for.