SimplyNZBs
simplynzbs.com · Debrid · 1 record · JSON
SimplyNZBs Debrid
deademailno cardRwrite-gated
| Free tier | None: the domain no longer hosts the indexer. A request for https://simplynzbs.com/ redirects to http://ww80.simplynzbs.com/?subid1=<uuid> - the shape of a lapsed domain on a parking service - and that host fails to answer (Cloudflare 520, 'the origin returned an unknown or empty response'). A review states the service is 'no longer operational as of 2024-2025'. The last published free tier was 10 API hits and 5 downloads per day, invite-gated. unit none; metered on none |
|---|---|
| Price | none stated |
| Per-object cap | not applicable: an NZB pointer file |
| Retention | last claimed 'up to 2,145 days retention' while operating; no longer served |
| Egress | none: every request is answered by a redirect to a parking host that does not respond |
| Identity | email Was invite-only: 'weekly 50 users get 10 invites each' plus a paid bypass. Today no registration path answers. |
| Limits |
|
| Binding | write-gated The service is gone, so the binding constraint is the one that killed it: no reachable write path at all. Recorded as write-gated because the vocabulary has no 'offline' kind and the verdict field carries that fact. |
| Interface | rest Was Newznab-compatible ('The SimplyNZBs API is compatible with ...' in its own invite page). Today the host redirects to a parking subdomain and /api?t=caps is answered by the same non-API redirect. endpoint: https://simplynzbs.com/api |
| Tooling | Nothing to configure: Prowlarr and NZBHydra2 cannot reach an indexer that does not answer. |
| Composes with | Nothing: removed from the stack. |
| Reliability | Dead: the name now redirects to a parking host. A client that still has it configured follows the redirect and gets a Cloudflare 520 or an empty result, not an auth error. |
| Notes | The verdict changed while the record was being written: the first two probes returned a 504, which reads as 'down', and a later probe returned 200 on the first hop, which looked like 'up'. Reading the redirect target settled it - the 200 was a redirect to a parking service. A session that stopped at the first probe would have written a different and wrong reason. |
| Evidence rung | reported The redirect to a parking subdomain was observed today, and that is strong evidence of a lapsed domain. The rung stays reported because the authoritative statement of death ('no longer operational as of 2024-2025') is third-party; the redirect alone does not date it. |
| Checked | 2026-10-24 (live); stale on 2026-11-07 |
Evidence (4)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | probe:https://simplynzbs.com/ | the request redirects to http://ww80.simplynzbs.com/?subid1=ba516fd4-ce86-11f1-9da0-c6ff21bde0c4, a parking host, which then fails with Cloudflare 520 'origin returned an unknown or empty response' |
| 2026-10-23 | probe:https://simplynzbs.com/api?t=caps | no Newznab document: the same redirect applies, so no API is served |
| 2026-10-23 | usenetreviewz.com/simplynzb-review/ | third-party: 'SimplyNZB is no longer operational as of 2024-2025' |
| 2026-10-23 | nzbhydra.com/indexers/ | third-party, still listing it: 'registration closed', 'VIP GBP 5 donation', '10 hits' |
More fields (4)
{
"price": "GBP 5 lifetime VIP (historical)",
"nzb_is_newznab": true,
"death_signal": "domain redirects to a parking host (ww80.simplynzbs.com) which answers 520",
"probe_sequence": "an earlier request in the same session returned a 504 from the broker; the later one showed the redirect. Both were kept rather than the first one reported as the truth."
}