iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The 112 no-signup mock URLs described by Supercrontab are a quick way to check how a client handles a preset HTTP status and response format. They cover 14 selected status codes across eight formats—not every possible status—and are best suited to lightweight functional checks. If a test needs custom request matching, delays, or other controlled behavior, use a configurable mock server instead.
What the 112 mock endpoints are
In an article by Emma on DEV Community, the catalog consists of hostnames in the pattern demo-{format}-{status}.supercrontab.com. The count comes from eight formats multiplied by 14 selected status codes: 8 × 14 = 112. The article describes these as fixed URLs that do not require signup; it does not establish that every URL is currently reachable, and the service was not independently tested for this article.
| Response format | Available status codes in the catalog |
|---|---|
| JSON | 200, 201, 204, 400, 401, 403, 404, 409, 422, 429, 500, 502, 503, 504 |
| XML | 200, 201, 204, 400, 401, 403, 404, 409, 422, 429, 500, 502, 503, 504 |
| TXT | 200, 201, 204, 400, 401, 403, 404, 409, 422, 429, 500, 502, 503, 504 |
| CSV | 200, 201, 204, 400, 401, 403, 404, 409, 422, 429, 500, 502, 503, 504 |
| HTML | 200, 201, 204, 400, 401, 403, 404, 409, 422, 429, 500, 502, 503, 504 |
| YAML | 200, 201, 204, 400, 401, 403, 404, 409, 422, 429, 500, 502, 503, 504 |
| RSS | 200, 201, 204, 400, 401, 403, 404, 409, 422, 429, 500, 502, 503, 504 |
| JavaScript | 200, 201, 204, 400, 401, 403, 404, 409, 422, 429, 500, 502, 503, 504 |
The DEV Community article shows a curl -i example returning HTTP/2 503 with a JSON body, and says browser calls are allowed through CORS. Those are claims in the article, not independent live-test results. The collection’s formats and status choices are reported by Emma’s DEV Community article; its linked index is Supercrontab.
Recommended Free Tools
What you can test with a fixed URL
A preset status is useful when the behavior under test depends mainly on the HTTP response code or a small sample payload. Emma describes these use cases:
#1 Best Overall
- Funny design. funny HTTP status code featuring a green thumbs up and the words "200 OK". A fun tee for any web developer or web programmer with a sense of humor
- Hardcover journal with 240 line-ruled pages (120 sheets)
- Built-in elastic closure and ribbon bookmark
- Includes an expandable inner storage pocket and a pen holder
- Retry decisions: check that a client retries a 503 but does not retry a 400, according to the client’s own policy.
- Parser handling: feed the client sample CSV or XML responses and check whether it can parse them.
- Error screens: return a 429 to exercise a frontend’s rate-limit message or recovery flow.
These are practical examples, not measured performance or reliability results. A successful response from a mock URL also does not prove that a real API behaves the same way.
How the static catalog differs from custom endpoints
The same DEV Community article describes a separate, account-based option for creating configurable endpoints. Do not confuse that feature with the fixed no-signup catalog: the static URLs offer the listed combinations, while the configurable endpoints are described as user-defined.
| Capability | Fixed catalog | Custom endpoints described in the article |
|---|---|---|
| Signup | Article says no signup is needed | Free account required |
| Status | 14 listed choices | User-defined status, according to the article |
| Body and content type | Preset response for each format/status URL | Article says users can set content type and a body up to 64 KB |
| Timing and failure behavior | Not described for the fixed URLs | Article says users can set a delay and error rate |
| Authentication and logs | Not described for the fixed URLs | Article lists optional Basic, Bearer, API-key, or HMAC authentication and request logging |
| Reported free-plan limits | Not stated | Article reports 3 endpoints, 30 requests per minute, and 500 requests per day |
The custom-endpoint features and free-plan quotas above are reported by the article author and were not independently checked; they should not be treated as a guaranteed current plan. The article identifies the Supercrontab index as a place for sample bodies, curl and fetch snippets, and retry notes, but those details are not independently established here.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →When to choose a configurable mock service
A fixed catalog is a poor fit when the test depends on how the server responds to a particular request, rather than only on a preset URL. For saved examples, custom headers or bodies, request matching, or controlled delays, a mock server gives more control.
Rank #3
- Quick reference Statistics chart
- This 8.5" x 11" 4-page laminated Guide provides an easy to follow summary of all basic principles that are the foundation to Statistics and Probabilities
- Detailed descriptions and examples of theory
- Using a combination of charts and sample equations, the key concepts are developed and the essential Statistics theories are outlined.
- Easy-to-read to promoted memory retention. Great quick reference aid.
Postman mock servers
Postman’s documentation describes mock servers based on saved response examples in a collection. Examples can include a response body, headers, and status; a request can select an example using a status-code header or match on the request body and headers. The documented response-delay header accepts 1–180,000 milliseconds. Creating a server through its API requires a Postman API key, and the guide says a created server is public by default unless configured as private. See Postman’s mock-server setup documentation.
Other status-testing endpoints
The current httpstatus.codes page lists GET-based status routes, delay and custom response-header options, as well as specialized routes for redirects, request inspection, streaming, response size, and encodings. The service says it requires no API key and permits 120 requests per minute; it describes itself as suitable for functional testing, not high-volume production or load testing. These are that service’s own claims, not features or quotas of Supercrontab.
Quick Recap
Pick the simplest option that covers your test
- Choose a fixed URL for a quick check of a client branch keyed to one of the 14 listed statuses, or for basic parser and error-interface checks.
- Choose an account-based configurable endpoint if the Supercrontab article’s reported controls fit your needs and you want to define a response yourself; confirm the current plan and limits with the service.
- Choose a mock server with saved examples and matching when the response must vary with request headers or body, or when repeatable delay behavior matters.
- Use a real staging API or dedicated test infrastructure when you need to validate production behavior, reliability, or load. The cited descriptions do not establish that these lightweight mock endpoints are appropriate for those purposes.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
