Docs

HiDHT is an IPFS CID checker built for quick retrieval diagnostics. It helps developers, storage operators, NFT teams, data publishers, and support teams answer a practical question: can this CID be found and retrieved from the public IPFS network?

The tool focuses on signals that matter during real troubleshooting: CID format validation, provider discovery through delegated routing, public gateway reachability, response timing, cache behavior, and clear error messages.

Every check starts with CID validation. HiDHT verifies whether the input looks like a valid IPFS CID before making network probes. This catches common mistakes such as truncated identifiers, pasted URLs, unsupported characters, or whitespace around a CID.

CID validation does not prove the content is online. It only confirms that the identifier is structurally usable for the next lookup steps.

HiDHT checks provider discovery through delegated routing and related IPFS routing endpoints. Provider records indicate that one or more peers have announced they can serve the CID or its containing block data.

A successful provider lookup is a strong discoverability signal, but it is not the same as a completed file download. Providers can be temporarily unreachable, behind slow networks, or advertising data that a gateway still cannot fetch within its timeout.

After provider discovery, HiDHT probes configured public gateways with safe request methods. Gateway results show whether common HTTP-based IPFS access paths can resolve the CID at the time of the test.

Gateway behavior may differ between providers. Some gateways block specific content types, enforce rate limits, rely on cache state, or time out while fetching uncached blocks from the network.

A healthy result usually has a valid CID, at least one provider signal, and one or more successful gateway responses. The timing data helps you distinguish fast cached retrieval from slower network fetches.

If providers are found but gateways fail, the CID may be announced but difficult to retrieve through public gateways. If gateways succeed while provider lookup is empty, the gateway may have cached the content or found it through routing paths not visible in the current lookup.

No provider results usually means the content is not currently announced, the provider announcement has expired, or the lookup path did not find an active provider. Re-pin the content, wait for provider records to propagate, and test again.

Gateway timeouts usually mean the gateway could not retrieve blocks quickly enough. Try another gateway, confirm the content is pinned by a reachable node, and check whether the CID points to a large UnixFS tree that needs more time to resolve.

HiDHT does not crawl the entire global DHT, inspect private node state, render remote files, classify content, or act as a permanent IPFS gateway. It is a diagnostic surface for availability signals, not a storage or hosting service.

The checker avoids downloading and displaying file contents. This keeps the product focused on retrieval metadata and reduces unnecessary exposure to arbitrary remote content.

Use HiDHT before sharing a CID publicly, after uploading content to IPFS, when a gateway URL fails, when NFT or dataset metadata appears unavailable, or when support teams need a neutral retrieval report.

HiDHT is also useful for monitoring demand discovery. Repeated manual checks can reveal whether users need scheduled checks, alerts, API access, or historical availability reporting for important CIDs.