How does Pingzo confirm a real outage vs a false alarm?

Pingzo uses a sliding-window failure detection algorithm. If 60% or more of the last 5 checks within a 30-minute window fail, we confirm an incident and alert you. This eliminates false positives from momentary network blips — you only get notified about real, sustained outages.

Do I need a WhatsApp Business account?

No! You just need a regular WhatsApp number. Pingzo handles the Business API integration on our end through Meta-approved BSPs. Simply enter your phone number, verify it, and you're ready to receive alerts.

Is the free tier really free?

Yes, forever. You get 1 monitor with 15-minute check intervals, email alerts, and a public status page with Pingzo branding. No credit card required, no time limit. Upgrade only when you need more monitors, faster checks, or WhatsApp/Telegram alerts.

Developer Tools

HTTP Status Code Checker

Inspect response codes, measure connection speed, verify SSL certificates, and check response headers.

HTTP Status Code Families

HTTP response codes are divided into 5 standard families. Learn how to classify response behaviors:

1xx Informational

Request received and continuing process. Rarely encountered in standard API checks (e.g. 101 Switching Protocols).

2xx Success

The action was successfully received, understood, and accepted. The baseline goal for active endpoints (e.g. 200 OK, 201 Created).

3xx Redirection

Further action must be taken by the user agent to complete the request. Indicates redirects (e.g. 301 Permanent, 302 Found).

4xx Client Error

The request contains bad syntax or cannot be fulfilled. Indicates user authorization or path issues (e.g. 400 Bad Request, 403 Forbidden, 404 Not Found).

5xx Server Error

The server failed to fulfill an apparently valid request. Indicates server outages or database deadlocks (e.g. 500 Internal Error, 502 Bad Gateway).

Common Status Codes Developers Debug

Use this standard reference guide to understand the meaning of common codes:

Status Code	Meaning / Description
200 OK	The request succeeded and the server returned the requested payload.
301 Moved Permanently	The target resource has been assigned a new permanent URI.
400 Bad Request	The server cannot process the request due to client-side syntax errors.
401 Unauthorized	The request lacks valid authentication credentials for the resource.
403 Forbidden	The client is authenticated but does not have permission to access the path.
404 Not Found	The server cannot find the requested URL path.
500 Internal Error	The server encountered an unexpected condition that prevented it from fulfilling the request.
502 Bad Gateway	The server received an invalid response from the upstream server.
503 Service Unavailable	The server is currently unable to handle the request (due to overload or maintenance).
504 Gateway Timeout	The gateway server did not receive a timely response from the upstream server.

Frequently Asked Questions

Common questions developers ask when validating API responses and headers.

How does the HTTP Status Code Checker work?

When you submit a URL, our cloud server sends a serverless HTTP request using the method you selected. It measures the round-trip response latency and parses the returned headers, response code, and SSL certificate credentials.

Can I check local API endpoints on my localhost?

No. Because this checker runs in the cloud, it cannot access your local network (`localhost` or `127.0.0.1`). To check a local API, you must expose it using a tunneling proxy (like ngrok) or inspect custom payload dispatches using our free Webhook Tester tool.

What is the user agent of the checker bot?

Our checking engine identifies itself with the User-Agent header: `Pingzo-Uptime-Bot/1.2 (+https://pingzoapp.com)`. If you have firewalls or strict cloud security rules (like Cloudflare or AWS WAF), you may need to whitelist this user agent.

How does Pingzo monitor status codes automatically?

When you configure a monitor in Pingzo, you define an "Expected Status Code" (e.g. 200). Our serverless checkers query your API at your plan's interval (e.g., every 1 minute) and trigger alerts if the response code doesn't match the expected code.

Monitor Status Codes Automatically

Stop checking URLs manually. Add your endpoints to Pingzo and receive alerts on WhatsApp, Telegram, or Discord when status codes deviate from expected values.

Start Free Monitoring