When HTTP 200 Means Down: Detecting Parked and Suspended Domains

There is a whole class of outage that classic uptime monitoring is blind to: the site that is technically “up” but completely dead to a visitor. The most common cause is boring and entirely avoidable — a domain registration lapses, or a hosting invoice goes unpaid, and the provider quietly replaces the real website with a parking page or an “account suspended” stub.

The cruel part is the status code. That placeholder page is served with a cheerful HTTP 200 OK. Your uptime checker sees the 200, paints the monitor green, and never alerts. Meanwhile every customer who types your address lands on a registrar advert or a “this account has been suspended” message.

Why uptime checks alone miss it

A plain HTTP check answers exactly one question: did the server return a successful response? A parked domain answers “yes” — the DNS resolves, the connection succeeds, and the registrar’s parking server cheerfully returns a 200 with a fully-formed HTML page. There is nothing at the transport or status-code level to distinguish it from your real site.

To actually notice the outage you have to look at what the page is, not just whether it loaded. That is a different job from a generic uptime ping, and it is exactly the gap PingZen closes.

A real example

Open https://soonar.ru/. It loads instantly, returns HTTP 200, and shows a tidy page — that says the domain is registered and parked at the registrar. There is no website there. A naive monitor would report it as up indefinitely; the owner would only discover the problem when a customer complained.

How PingZen detects it

PingZen runs three independent, low-false-positive layers on every HTTP/HTTPS check. Any one of them is enough to mark the monitor DOWN, open an incident, and fire your alerts.

1. Content fingerprints. The response body is normalised (HTML tags stripped,   decoded, whitespace collapsed) and matched against a curated list of high-precision parking and suspension phrases in English and Russian — the exact wording registrars and hosts use on their placeholders (REG.RU, Timeweb, RU-CENTER, cPanel’s “this account has been suspended”, and others). Generic prose never trips it; only the specific placeholder text does.

2. For-sale marketplace hosts. A redirect or page pointing at a known parking marketplace — Sedo, Afternic, Dan.com, ParkingCrew, Bodis.

3. Nameserver delegation. This is the content-independent layer, and it is the one that catches the cases the other two miss. PingZen resolves the domain’s authoritative nameservers and matches them against dedicated parking nameservers. A for-sale lander is often rendered entirely in JavaScript and exposes nothing useful in its HTML — but the domain is still delegated to Afternic or Sedo, and that delegation gives it away. In testing against real for-sale domains, this layer flagged every resolvable one, including those the content scan saw nothing in.

When a monitor trips one of these layers it is labelled Stub Page, and the detail view shows a banner explaining it is a registrar parking or hosting-suspension placeholder, with advice to check domain renewal and hosting status.

A note on Russian registrars

One honest caveat. Russian registrars (REG.RU, nic.ru, Timeweb) serve their parking pages from shared nameservers — the same ones live sites use — so the nameserver layer deliberately ignores them to avoid false positives. For those, the content-fingerprint layer does the work instead. The nameserver layer’s strength is international dedicated-parking services; the content layer carries the Russian-hoster cases. Together they cover both.

Turning it on

Detection is on by default for new and existing HTTP/HTTPS monitors — there is nothing to configure. If you ever want to disable it for a specific monitor (say, you deliberately monitor a parked domain), open the monitor form and turn off “Detect parking/stub pages” in the HTTP advanced options.

The takeaway

“Returns 200” is not the same as “works”. An expired domain or suspended host is one of the most embarrassing outages precisely because everything looks fine on a status dashboard. PingZen treats a parking or suspension page as what it really is — downtime — so you hear about it from your monitor, not your customers.

For the full reference, see the Parked & Stub Page Detection docs.