fshy

fshy / Debrid

SwiftSeedbox

swiftseedbox.com · Debrid · 1 record · JSON

SwiftSeedbox Debrid

deadanonymousno cardM

www.swiftseedbox.com/ · former seedbox host (domain does not resolve) · debrid/swiftseedbox · JSON · compare

Free tiernone: swiftseedbox.com does not resolve. DNS over HTTPS returns NXDOMAIN (Status 3) and a local lookup returns 'Could not resolve host'.
unit none; metered on none
Pricenone stated
Per-object capnot applicable: no service
Retentionnot applicable: no service
Egressno service to assess
free_allowance: none
Identityanonymous not applicable; nothing can be registered
Bindingnone no constraint applies to a name that does not resolve
Interfaceunknown no interface: the name has no DNS record
Toolingnone
Composes withremoved from the candidate set; nothing resolves, so nothing can be ordered or retrieved
ReliabilityNXDOMAIN at the registry level, not a blocked fetch: the name is not delegated
NotesA brief that names SwiftSeedbox should treat it as gone. The check is cheap to repeat: one DoH query. If the name is re-registered, this record is stale rather than wrong, and must be re-probed before use.
Evidence rungmeasured Measured by probe on 2026-10-23: Cloudflare DoH for swiftseedbox.com returned Status 3 (NXDOMAIN) with the .com authority section and no answer; curl returned 'Could not resolve host'. swiftseedbox.ch was tried too and also did not resolve.
Checked2026-10-24 (live); stale on 2026-11-23
Evidence (1)
datesourcewhat it proved
2026-10-23probe:https://www.swiftseedbox.comDoH 'Status: 3' (NXDOMAIN) for swiftseedbox.com, A query; curl exit 6 'Could not resolve host' for www.swiftseedbox.com and for swiftseedbox.ch
More fields (2)
{
 "death_evidence": "NXDOMAIN at the .com registry",
 "probe_commands": "curl 'https://cloudflare-dns.com/dns-query?name=swiftseedbox.com&type=A' -H 'accept: application/dns-json'; curl -sS -o /dev/null -w '%{http_code}' https://www.swiftseedbox.com/"
}
Unknown or withheld values (1)
  • $.interface interface-unknown