- Free allowance
- No account and no key.
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- measured4 sources; a live request was made and its output kept
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | No account and no key. GET /search?q=linux returned 98,890 bytes of results, paginated to 174 pages. GET /nzb?q=linux&<base64 collection id>=on returned a 4,229-byte NZB carrying 9 files. The site publishes no daily counter anywhere a reader can reach. unit unlimited; metered on none; 'unlimited' is a statement about the absence of a published quota, supported by a 6-request burst, not by a vendor sentence. |
|---|
| Price | none stated |
|---|
| Limits | - request-rate none observed: 6 consecutive anonymous searches in one session all returned 200
Page depth is the only ceiling the service shows: the query 'linux' exposed 174 pages. No per-IP shaping was observed and no quota page exists to read. |
|---|
| Binding | none Nothing in the seven-kind vocabulary fails at a client pulling 1 TiB a month: there is no counter to hit. The real cost is two GETs per NZB plus a scraper that survives a front-end rewrite, which is a tooling cost and not a limit. |
|---|
| Identity | anonymous No account, no key, no cookie. Search and NZB creation both answered an anonymous request with no credential of any kind. |
|---|
| Egress | No metering. Every answer is a small XML pointer file; the bytes themselves come from whichever news provider a user holds an account with. |
|---|
| Per-object cap | not applicable: the answer is an NZB pointer file (4,229 bytes, 9 files), never the payload |
|---|
| Retention | not stated on the pages read. A third-party indexer comparison claims 'up to 1,100 days of binary retention, searches 400+ popular newsgroups by default' (nzbhydra.com, 2026-10-23). |
|---|
| Interface | rest HTML search over HTTP GET against /search (Next.js front end, results server-rendered). NZB is built by a GET to /nzb?q=<query>&<name>=on where <name> is the base64 collection id carried by each result's checkbox. There is no Newznab endpoint: /api returns 404. |
|---|
| Tooling | No Newznab API, so Sonarr, Radarr, Prowlarr and NZBHydra2 cannot add it as an indexer. A wrapper must GET /search, parse the collection ids out of the checkbox names, and re-issue GET /nzb. Two GETs per download. |
|---|
| Composes with | A fallback name search when every Newznab indexer is down or refuses registration; the NZB it returns goes into the same SABnzbd or NZBGet queue as any other. |
|---|
| Reliability | Advertiser-supported binary search engine; results are raw article headers, so completion depends entirely on the retention of the news provider a user pays, and dead posts stay listed until the indexer notices. |
|---|
| Notes | The result page is a Next.js front end but the results are server-rendered, so the HTML carries them; that is why a plain GET works where NZBIndex's does not. |
|---|
| Evidence note | measured Search and NZB creation were both run today and both produced payload bytes with a recorded digest. Nothing here is quoted from a third party. What would raise nothing: the rung is already the top one; what is missing is a long-run rate test, which a 6-request burst does not provide. |
|---|
| Parsed numbers | |
|---|