By RamthaMedia
RamthaMedia Free eBooks · August 2026
Price: Priceless
· 13 min read
Preface
This book is for anyone who has ever migrated a site, merged two domains, or built an automation that quietly stopped working. You will finish knowing exactly what HttpStatus checks, how its API and bulk tools differ, and where its free plan actually stops. It does not cover pricing tiers or account setup screens, since neither was part of what this book draws from.
Chapter 1
What Actually Happens When a Browser Hits a Redirect
Three weeks after a content team folds two blogs into one domain, someone finally asks why organic traffic dropped by a third. Nobody rewrote a single sentence. What moved were the addresses those sentences lived at, and the redirects meant to carry readers and search engines from the old ones to the new ones quietly didn't do their job.
A redirect is a server telling a browser, in one line, to try somewhere else. The server sends back a 3xx status code and a Location header, and the browser makes a second request to whatever address that header names. If the new address also redirects, the browser makes a third request, and so on – each one a full round trip before the reader sees anything.
Search crawlers follow the same chain, with one hard limit: past five hops, Googlebot stops and never lands on the final URL at all. A migration plan that routes old pages through two or three intermediate redirects before reaching the real destination can lose pages from search entirely, and nothing about the site's own pages would show it.
Checking this by hand means opening developer tools, watching the network tab, and counting hops one migration at a time. HttpStatus does the same trip in one request – a URL goes in, and every hop in the chain comes back with its own status code, headers and timing, in the order a browser would actually see them.
The four permanent- and temporary-redirect codes – 301, 302, 307 and 308 – look similar on paper and behave differently under the hood. What separates them isn't the number itself but what each one promises about whether a request method survives the jump, and that promise is the thing worth checking before trusting a migration plan to a single status code.
What you can actually do here
Before anything else, here is what HttpStatus actually lets you check – grouped by the kind of problem each group solves, with the chapter that walks through it.
Reading one redirect chain in full
| Use | Who it fits | Where | Worth knowing |
|---|---|---|---|
| See every hop in a redirect chain, not just the final destination | SEO specialists mid-migration | Web interface → paste URL → expand the row with the blue arrow | Shows status, headers and latency per hop Detail view covers one URL at a time |
| Pull the response body of the final URL, not only its headers | Developers debugging what a redirect actually lands on | API POST body → includeResponseBody: true | Confirms what actually renders at the end Off by default |
| Test a URL as Googlebot, GPTBot or ChatGPT-User instead of a browser | Technical SEOs chasing bot-specific redirects or cloaking | userAgent field → choose a predefined string | Reveals redirects that only fire for specific crawlers Custom strings still identify the request as coming from HttpStatus |
| Break a hostname into domain, subdomain and public suffix automatically | Anyone auditing URLs across many top-level domains | API → includeHostInfo: true | Handles ICANN and private suffixes without manual parsing Only returned when explicitly requested |
| Measure exactly where a slow redirect loses its time – DNS, TLS, or the wait for first byte | Performance engineers chasing a sluggish redirect | API → includeTimings, phases object | Breaks total time into named phases Comes back as a nested object, not one summary number |
| Confirm whether a redirect stays on the same domain or jumps to a different one | Anyone verifying link value survives a migration | Response chain → compare origin of each hop | Flags cross-origin hops explicitly |
Checking many URLs without writing code
| Use | Who it fits | Where | Worth knowing |
|---|---|---|---|
| Paste up to 100 URLs at once and get status codes for all of them | Auditors after a site migration | Web interface → paste list → Check status | No file upload required Hard cap of 100 per batch |
| Export results straight into a connected Google Sheet | Teams who need a shareable audit record | Settings → Data export tab → paste Sheet URL → grant Editor access | Writes without reading anything already in the sheet Must be configured once before the export button works |
| Slow requests to the same host so its server doesn't start throttling back | Anyone checking many URLs on one small server | Settings → Throttle requests → 100/10/5/2/1 per second | Prevents 429s and timeouts mid-audit Default fires up to 100 requests at once |
Automating checks so nobody has to remember to run them
| Use | Who it fits | Where | Worth knowing |
|---|---|---|---|
| Trigger a status check from a Make scenario with no code | Ops teams already using Make | Make → HttpStatus app → Get HTTP Status action | Reads URLs from Sheets or Airtable directly Free-plan throttling still applies inside the scenario |
| Schedule recurring checks in n8n against a Baserow or NocoDB table | Teams monitoring link health over time | n8n → Schedule Trigger → HTTP Request node → api.httpstatus.io/v1/status | Writes results into a second table automatically Both tables have to be built by hand first |
| Run status checks from inside an Airtable base using its scripting extension | Airtable-based content teams | Airtable → Extensions → scripting extension → paste script | No external automation tool needed Scripting requires a paid Airtable plan |
Testing how your own tools handle failure
| Use | Who it fits | Where | Worth knowing |
|---|---|---|---|
| Force a specific status code on demand to test error handling | QA engineers and developers writing error-handling code | mock.httpstatus.io/{code}, e.g. /503 | Covers the full range from 200 to 511 Always responds to GET, unlike some real-world status conditions |
| Simulate a redirect chain of a chosen length with a delay on each hop | Developers testing timeout handling before launch | Mock endpoint → redirect params → hop count + delay in milliseconds | Delay configurable per hop Capped at 25 simulated redirects per chain |
Chapter 2
One URL, One Request, Every Detail the API Returns
A developer wiring a link-checker into a build pipeline has one requirement a web page can't satisfy: something that answers programmatically, the same way every time, without a human clicking a button. That's what the HttpStatus API is built to do.
The API endpoint takes a single POST request with a JSON body and a URL field, and it accepts only one URL per request – the trade-off for the batching the web interface offers is depth per call rather than volume per call. The response mirrors what the web interface shows: status code, status message, and the full redirect chain if there is one.
Everything past the basics is opt-in. Response headers, request headers, the raw request line, the response body of the final URL, host-info parsing, and full timing data are each a separate flag in the request body. A minimal check returns quickly; a fully detailed one returns everything needed to debug a redirect without a second tool.
One flag decides how many redirects the API will follow before giving up: it defaults to ten, and a request that exceeds that number is aborted with an error rather than silently truncated. That default protects a caller from an infinite loop consuming its own request budget, but it means a nine-hop legacy migration will complete while a twelve-hop one needs the limit raised explicitly.
The user-agent field is where the API stops being just a status checker. Sending a request as googlebot-desktop, bingbot-mobile, applebot, gptbot or chatgpt-user – alongside a genuine browser string – can surface a redirect or a block that only exists for one of those visitors, which is precisely the kind of thing a plain browser tab will never reveal.
You may also like:
What Hostinger Actually Runs Behind One Login
Chapter 3
Checking a Hundred URLs Without Touching a Line of Code
An SEO auditor inherits a spreadsheet of three hundred URLs after a client's site migration, and the client wants to know by Friday which ones are broken. Opening each one individually isn't a plan; it's a way to lose Friday.
The web interface handles this without any file upload: paste up to a hundred URLs into the textarea and click Check status. Each request URL comes back with its status code and, where relevant, its full redirect chain – visible at a glance, expandable per row for the detail behind it.
Checking many URLs on the same host at once creates its own problem: HttpStatus sends up to a hundred simultaneous requests by default, and a server without spare capacity may respond with 429 Too Many Requests, or simply stop responding at all. The Throttle requests setting in Settings lowers that to 10, 5, 2 or 1 request per second, trading speed for a server's willingness to answer honestly.
Results don't have to live only on screen. The Data export tab connects a Google Sheets document, and once that connection is granted Editor access, an Export to Sheets button writes the filtered results – request URL, status code, destination and any error message – directly into it. Running the same batch again and exporting again appends a fresh set of rows rather than replacing the last one.
A hundred URLs a batch is generous for a spot audit and thin for anything larger. Past that ceiling, the choice isn't a bigger textbox – it's the API, run in a loop, which is exactly what the next chapter is built around.
Chapter 4
Wiring HttpStatus Into Make, n8n, Airtable and Retool
Somewhere between 300 URLs and 3,000, manual checking stops being a task and starts being a job nobody wants. HttpStatus is built to be called from four no-code and low-code tools instead of a browser tab, and each one solves the same problem with a different shape of workflow.
The Make integration reads a list of URLs from a connected Google Sheet or Airtable base, sends each one through the HttpStatus app's Get HTTP Status action with a one-second delay between requests, and writes status codes, redirect counts and full chains back into a results tab. The whole scenario runs on a schedule, with no code written at any step.
n8n follows the same shape aimed at Baserow or NocoDB instead: a Schedule Trigger starts the run, a node pulls every row from a source table, a loop sends each URL to the API with the required X-Billing-Token header, and a second node writes the response into a results table mapped column by column, including up to ten redirect hops per row.
Airtable takes a different route – its scripting extension runs JavaScript directly inside the base, calling the API in a loop and creating status columns on the fly if they don't already exist. Retool builds the same idea as a visible workflow of blocks: a trigger, a query that fetches URLs, a loop that calls the API, and a final step that appends results to a second sheet tab.
None of the four is more capable than the others in what it can call – they all hit the same single-URL endpoint with the same one-second-per-request ceiling on the free plan. What differs is which tool a team already lives in, and whether they want a workflow they can see laid out in blocks or one that runs invisibly on a schedule.
You may also like:
Getting the Most From Snapgen Before the Credits Run Out
Chapter 5
A Mock Endpoint Built for Breaking Things on Purpose
A developer finishing a link-checking library has tested it against real sites for a week and still doesn't know for certain how it handles a 508 Loop Detected, because nothing in their test suite has ever actually returned one. Waiting for a real server to misbehave on schedule isn't a testing strategy.
The mocking service at mock.httpstatus.io exists to manufacture exactly that. Appending any supported status code to the URL – /404, /429, /508 – returns a response carrying that exact code, on demand, every time. The service always answers using GET, which the documentation is upfront about not being representative of every real-world condition a status code might depend on.
Beyond single codes, the same service simulates a redirect chain of a chosen length, with a configurable delay applied to each hop and to the final response – useful for testing whether a piece of code times out gracefully or hangs when a real chain runs slow. Delay accepts a value between one millisecond and sixty seconds.
Two response headers confirm a test actually did what it was supposed to: x-response-time reports the total time including any delay applied, and server-timing reports the delay duration in a structured format such as delay;desc="Delay set";dur=1000. Reading either beats trusting a stopwatch to confirm a test setup worked.
A chain capped at 25 simulated hops and a delay capped at 60 seconds per hop cover most realistic testing scenarios without turning the mock service into infrastructure of its own – which is precisely the boundary a synthetic test endpoint should hold.
Chapter 6
What the Free Plan Actually Limits, and How Cancellation Really Works
One request per second. That's the ceiling the free plan places on the API, stated plainly in the integration tutorials rather than on a features page, and it's the number that decides whether an automation built on Make or n8n needs a deliberate delay step or runs into 429 responses within its first few executions.
Subscriptions renew automatically at the end of each billing period unless cancelled beforehand, and cancellation has exactly one supported path: through the subscription dashboard provided by the account gateway. Attempting to cancel through the payment processor directly is explicitly unsupported and can end access immediately, without the pending-cancellation window a proper cancellation gives.
Annual subscriptions carry a one-way rule worth knowing before choosing one: they can be upgraded to a higher tier, but never downgraded or converted to a monthly plan. A team unsure whether their usage will stay steady has more flexibility starting monthly than starting annual.
Account creation requires being at least 18 years old, and the service's own operational logs – kept by its hosting providers rather than the company directly – are retained for roughly 30 days for security and performance purposes, never for tracking or marketing, and the company does not extend that window.
None of these are limits a features page volunteers, which is exactly why they belong in a decision rather than a footnote. If your goal is an occasional audit after a migration, the free plan's one-request-per-second ceiling is unlikely to matter. If your goal is continuous monitoring across thousands of URLs on a schedule, that same ceiling is the number your automation has to be built around from the first workflow step, not discovered after the tenth failed run.
Questions readers actually ask
Does HttpStatus follow redirects created with JavaScript?
No. It follows only server-side redirects sent as HTTP responses; a redirect created in the browser with JavaScript or a meta refresh tag happens entirely on the client's device and is outside what a server-side checker can see.
What's the real difference between a 401 and a 403 response?
A 401 means the request lacks valid authentication credentials at all. A 403 means valid credentials were provided but the account still isn't authorized to access that resource – a permissions problem rather than a login problem.
Why would Google never reach a page after five redirect hops?
Googlebot stops following a redirect chain past five hops and does not land on the final destination URL, which is why long migration chains can quietly remove pages from search results even though every individual redirect works.
Can HttpStatus check a URL that sits behind a login?
Yes, for HTTP Basic Authentication – the username and password can be sent in the Authorization header of the request, the same way a script or browser would authenticate against that kind of protected resource.
Can I check more than one URL in a single API call?
No. The API processes exactly one URL per request. Checking many URLs at once is either done through the web interface, which accepts up to 100 URLs in one batch, or by looping API calls in an automation tool.
What happens if I check URLs on several different slow-responding hosts at once?
If servers behind one or more of those hosts don't respond in time, timeout errors occur for those specific URLs, and depending on load, can affect subsequent requests in the same batch as well.
How many redirects will the API follow before giving up?
Ten, by default. That number can be raised or lowered per request, and exceeding the configured limit aborts the check with an error rather than returning a partial or incorrect result.
Does HttpStatus keep a record of every page it checks?
The company itself does not maintain long-term logs of checked pages. Its hosting providers retain short-term operational logs – on the order of 30 days – for security and performance purposes only, not for tracking or marketing.
Can I cancel a subscription directly through the payment processor?
No. Cancelling through the payment processor rather than the subscription dashboard is unsupported and can end access immediately, without the pending-cancellation period a proper cancellation provides.
What's the minimum age to create an account?
18. Anyone younger is not permitted to create an account or use the service under its terms.
Can the mock endpoint return JSON instead of HTML?
Yes. A response parameter lets a request specify either text/html or application/json as the content type of the mocked response.
Can I set custom response headers on a mock request?
Yes, using a header-value parameter format, and multiple values for the same header name can be combined with a comma.
What's the difference between a 404 and a 410 response?
A 404 signals uncertainty – the resource might return in the future. A 410 signals a deliberate, permanent removal, and search engines typically de-index a 410 URL faster than one repeatedly returning 404.
Can an annual subscription be switched to monthly billing later?
No. Annual subscriptions can be upgraded to a higher tier but cannot be downgraded or converted to a monthly plan.
Cover photo: Photo by Paul Seling on Pexels. Illustrative image — not a screenshot of the site described.
Official source links:
HttpStatus
Disclaimer: This eBook is compiled from publicly available information and was accurate at the time of writing. For full and up-to-date details, please visit the official website linked above. RamthaMedia accepts no legal liability for any decision made on the basis of this eBook, and nothing here is professional, financial or legal advice.
