Checks against a host you have not proven to own are limited, so that PingWise cannot be used to hammer someone else's server. Verifying a domain lifts the limits for that domain and all of its subdomains.
What an unverified host gets
- HTTP(S), TLS and ping checks only, on ports 80 and 443.
- One check a minute at the fastest.
- GET or HEAD requests with harmless headers only: no custom methods, bodies, basic auth or credential headers.
What verification unlocks
- TCP, SMTP and DNS monitors, on any port.
- 15-second checks, and 10-second checks once the account has bought credits.
- Custom methods, request bodies, basic auth and secret headers.
How to verify
Monitors → Domains → Add domain. You get a token, and either of these proves the domain:
- A DNS TXT record named
_uptimebox.<your-domain>with the valueuptimebox-verify=<token>. We look it up through 1.1.1.1, 8.8.8.8 and 9.9.9.9, so it works as soon as those resolvers see it. - A file at
https://<your-domain>/.well-known/uptimebox-verify.txtcontaining the token. The TXT record is tried first, then the file over HTTPS, then over HTTP.
Two more sources count without a token:
- a domain that is an active zone in a Cloudflare account you have connected to PingWise;
- a domain whose nameservers are under a domain you already verified, the usual case for a hosting provider's customers.
If that source goes away, the verification is kept for 30 days and then lapses.
Removing a domain from the list leaves its existing monitors running. For a reseller, verified domains also cover its customers' accounts.
Last change: 31 October 2026.