StatusLab.dev
Test HTTP status codes for your application with ease
How It Works
Use StatusLab.dev to test how your applications handle different HTTP status codes. Simply enter a code above or use one of the endpoints below.
Status Code Categories
Informational (100-199)
Informational responses indicating that the request was received and understood.
Success (200-299)
Success responses indicating that the request was successfully received, understood, and accepted.
Redirection (300-399)
Redirection responses indicating that further action needs to be taken to complete the request.
Client Error (400-499)
Client error responses indicating that there was an error with the request.
Server Error (500-599)
Server error responses indicating that the server failed to fulfill a valid request.
Integration Examples
curl -i https://statuslab.dev/418// Using fetch
fetch('https://statuslab.dev/401')
.then(response => {
console.log(`Status: ${response.status}`);
return response.json();
})
.then(data => console.log(data))
.catch(error => console.error('Error:', error));// Using HttpClient
using System.Net.Http;
using System.Text.Json;
var client = new HttpClient();
var response = await client.GetAsync("https://statuslab.dev/500");
Console.WriteLine($"Status: {(int)response.StatusCode} {response.StatusCode}");
if (response.Content.Headers.ContentLength > 0)
{
var content = await response.Content.ReadAsStringAsync();
Console.WriteLine($"Content: {content}");
}import requests
response = requests.get('https://statuslab.dev/201')
print(f"Status: {response.status_code}")
print(f"Content: {response.json()}")About StatusLab.dev
StatusLab.dev is a tool powered by EverUptime to help developers test how their applications handle different HTTP status codes. This tool is especially useful for testing monitoring systems, API integrations, and error handling in web applications.
All endpoints are cached and served over CDN for fast response times worldwide.