HTTP & HTTPS Monitors
The default check for web endpoints.
Configure HTTP monitors — URLs, expected status codes, timeouts, custom headers, and follow redirects.
Creating an HTTP monitor
On Monitors → Add Monitor, select HTTP(S) and enter the full URL including https://. SurePing records status code, response time, and whether the connection succeeded.
Set expected status codes — typically 200, or 200–299 for APIs. If your endpoint legitimately returns 401 without auth, include that code in the allowed list.
Advanced options
Custom headers (JSON) let you send API keys or auth tokens. Timeout defaults are suitable for most sites; lower them for latency-sensitive APIs.
HTTP monitors follow redirects up to a sensible limit and report the final status code and total time — useful for catching broken redirect chains.
Firewall and WAF whitelisting
SurePing identifies itself with the user agent string: Mozilla/5.0 (compatible; SurePing/1.0; +https://sureping.cc). If your site uses a Web Application Firewall (WAF), bot-protection service such as Cloudflare Bot Management, or strict firewall rules, you may need to allow this user agent to prevent checks from being blocked.
Blocked requests typically show as false-positive down alerts with status codes like 403 or 503. If you see these after adding a monitor, check your WAF or firewall rules and whitelist the SurePing user agent.