Website uptime · content · traffic monitoring

When your site goes down,
you should be the first to know.

Paste a URL and start monitoring in 30 seconds. Unreachable, certificate expiring, page errors, price or version changes, a sudden traffic drop — we're watching and we alert you when something breaks.

No credit card · checks as fast as 1 minute · email / DingTalk / webhook / browser push

1min
Fastest check interval
3times
Alerts only after consecutive failures — flapping never disturbs you
Multi-region
Second confirmation to rule out problems with the monitoring machine's own network
90days
Free trial, no credit card
Three steps

No monitoring skills needed.
Just a URL.

Everything else — name, certificate check, check frequency, where alerts go — we decide for you, and every decision is written on the result page, editable anytime.

Paste URL

There's just one input box. A bare domain works too — we add the scheme and read the page title as the site name.

https://www.example.com → Monitoring started · Up · 244 ms

We're watching

A visit every few minutes checks status code, content, certificate, and response time; on failure, another region confirms first.

14:32:01 200 231ms
14:37:02 200 248ms
14:42:03 timeout → confirming multi-region…

Alerts when things break

Email, DingTalk, webhook, or browser push. One incident sends one down alert + one recovery — never a mail every minute.

▲ Incident Mall shop.example.com
unreachable 3 times in a row · lasting 6 min
— you'll be notified again when it recovers
What monitoring can do

More than just "it loads".

Most "broken sites" still return HTTP 200: a database error printed on the page, a certificate expiring tomorrow, a wrongly edited price, a script 404 leaving a blank page, a silent JS exception. We watch all of it.

Uptime and response time

Status code, keyword checks, blank-page detection, slow-response threshold. Every 1–10 minutes; consecutive failures required before calling it an incident.

Page error detection

HTTP 200 but the page is a PHP error page? WordPress can't reach its database? A framework exception page? We recognize 15 classes of server-side errors and show you the actual text.

HTTPS certificate

Staged reminders 30 / 7 / 3 / 1 days before expiry; handshake failures and expired certificates alert immediately.

Content watch

Watch a price, version number, stock status, or any text on a page — get notified when it changes. Say "watch the price" and AI locates it for you.

Real-browser check

Page 200, resources 200, but the JS throws, an API 500s, CORS blocks a critical script — you only know by really opening it. A platform Chromium node does it for you once a day.

Multi-region speed test and DNS check

Measure each segment's response time from multiple vantage points to find which region is slow and where; verify public DNS resolution matches the IP actually connected.

Resource check

Whether the scripts, styles, and images a page references actually load, and any mixed content — the 404s you'd see in a browser console, without opening a browser.

Notifications on every device

Email, DingTalk, webhook, plus browser push — no app needed; alerts land right in your phone and desktop notification centers. Route by severity and time of day.

Team and on-call

Members come in owner / member / read-only roles; an on-call rotation decides who gets this week's alerts; a public status page for clients or the office wall screen.

See all features →

Beyond monitoring

People managing hundreds of sites
need more than "is it down?".

Traffic, snapshots, server inventory, business metrics — everything you'll worry about once your site fleet is running, in the same console.

Traffic analytics

A <3KB script: visitors, pageviews, currently online, referrers, UTM, search terms, 404s, time on page. No cookies, no raw IP storage; visitor IDs rotate daily.

Learn more →

Page snapshot evidence

A real browser captures a full-page screenshot and the rendered DOM; per-file hashes + platform signature + public timestamp. A competitor's price, a promise on someone's page, how things looked before the edit — keep a verifiable record.

Learn more →

Server inventory

Sites are grouped under the server their IP actually points to. Register the provider and expiry date; renewal reminders 30 / 14 / 7 / 3 / 1 days ahead; when a whole machine has an incident, its alerts merge into one.

Learn more →

Stability

All sites ranked by uptime, with incident-cause breakdown and incident-duration archive. Postmortems, monthly reports, and disputes with your provider — all documented.

Learn more →

Site tools

Baidu index count, PC authority weight, ranked keyword count — third-party business-data APIs, tracked as trends. Billed per query against your quota; every plan includes a monthly allowance.

Learn more →

Bulk import and groups

One spreadsheet imports hundreds of sites; groups keep them organized; Trash catches mistakes. The order problems that come with scale were thought through from day one.

Learn more →
Why it's trustworthy

The biggest risk of a monitoring tool
is that it can't be trusted itself.

False alerts make people mute notifications; missed alerts mean learning about it from customer complaints. Every rule in WebCheck was paid for by a real incident.

Security and trust, in detail →

Alert only on consecutive failures

A single timeout is not an incident. Three consecutive failures by default — network flapping won't wake you at midnight.

Multi-region second confirmation

After the monitoring machine calls a failure, another vantage point tries once more — it can tell whether the site is really down or the monitoring machine's own network has a problem

Own-incident circuit breaker

When the monitoring uplink dies, every site "fails at once". We recognize this pattern and send one system notice — not hundreds of false alerts.

One incident, one down alert + one recovery

Never repeats every minute. A site that keeps flapping is folded into the daily digest instead of a constant disturbance.

Gentle on your server

Sites on the same server are rate-limited and staggered. We once got ourselves blacklisted by a firewall for checking too fast — so now we don't.

Tenant data isolation

Every query carries a tenant condition, and automated tests hit every ID-taking route as another tenant to prove it can only get a 404.

Pricing

Use it for 90 days, then decide.

No credit card for the trial. When it ends, site checks stop but your configuration and history are kept.

Trial

¥0/ 90 days
 

Full features, use first, decide later. No credit card.

  • 10 sites · 5 content watches
  • Checks as fast as 10 minutes
  • Built-in vantage points (Hong Kong / mainland)
  • Email / DingTalk / webhook / browser push
  • 2 members · traffic analytics · snapshot evidence
  • 100 tool quota credits per month
Start trial
Most popular

Basic

¥19.8/ Month
¥198/ Year
Billed monthly, cancel anytime
= ¥16.5/mo · save ¥39.6

Solo site owners and small teams.

  • 50 sites · 20 content watches
  • Checks as fast as 5 minutes
  • Built-in vantage points + 1 self-hosted node
  • Email / DingTalk / webhook / browser push
  • 5 members · status page · traffic analytics
  • 300 tool quota credits per month

Pro

¥59.8/ Month
¥598/ Year
Billed monthly, cancel anytime
= ¥49.8/mo · save ¥119.6

Ops teams and maintenance providers.

  • 200 sites · 100 content watches
  • Checks as fast as 2 minutes
  • Built-in vantage points + 3 self-hosted nodes · multi-region speed test
  • Every channel · on-call rotation
  • 20 members · status page · traffic analytics
  • 1500 tool quota credits per month

Hundreds of sites? Team ¥199/mo: 500 sites, 1-minute checks, 10 nodes. Full comparison on the pricing page.

FAQ

You might ask

How is this different from writing a curl script myself?
A script can tell you "it's unreachable"; it can't tell you "reachable but showing an error page", "the certificate expires in 3 days", "is the site down or did your own network blip", "the page's JS is throwing". More important is alert discipline: a script mails you every single minute an incident lasts.
Will there be false alarms?
This is what we care about most: 3 consecutive failures before calling it an incident, multi-region confirmation, monitoring self-failure circuit breaker, flapping suppression — each exists so every alert you get is worth reading. See Security and trust.
Will the checks put load on my server?
No. Each site gets one GET request every few minutes — about the same as one visitor. Multiple sites on the same server are rate-limited and staggered. Heavier checks like resource checks run only once a day.
Can you run monitoring on my sites in mainland China / overseas?
Yes. Our monitoring probes are in Hong Kong and can reach most regions directly. For sites the probes can't reach but yours can, you can route checks through your own node or proxy.
Where is the data stored, and is it safe?
Data lives on servers in Hong Kong, strictly isolated per tenant, HTTPS end to end, passwords stored as hashes only. We never read the content of the pages you're monitoring for any other purpose. See the privacy policy.
What happens to my data when the trial ends?
Site checks stop, but configuration and history are fully kept. Upgrading resumes instantly. We email a reminder before it expires.

Next time your site breaks,
let the alert reach you before your customers do.

90-day free trial, no credit card. Paste a URL and start today.