The interval is set on each target, but not every check runs on that schedule. WebCheck also applies a minimum cadence for each check type, and your plan may require a longer interval.
What happens when I add a site?
The first checks are queued straight away. After that, WebCheck uses the target interval, subject to each check type’s minimum cadence and your plan’s limit.
Can I check it immediately?
Yes. Use Run now when you want a fresh result outside the normal schedule. Manual checks do not require you to wait for the next scheduled run.
Why do checks run at different times?
Under the current defaults, HTTP and TCP checks run no more often than every five minutes, DNS checks every three hours, and TLS, domain-expiry and security-header checks daily. A longer target or plan interval slows those schedules further.
What if a request fails?
A connection failure on an HTTP check can be retried every 10 seconds for up to 60 seconds within that run. A returned HTTP status such as 500 or 429 is recorded and evaluated without that retry loop.
Changing the schedule
Edit the target to choose an interval your plan allows. The change affects future runs; it does not remove earlier history or incidents.