What does HiDHT check?

HiDHT validates IPFS CIDs, checks provider discovery through routing endpoints, and probes public gateway availability without rendering content.

Does HiDHT download IPFS content?

No. HiDHT focuses on retrieval metadata such as provider count, HTTP status, latency, cache state, and troubleshooting notes.

IPFS retrieval health

Check IPFS CID availability

Test provider discovery and public gateway retrieval for IPFS content. HiDHT returns technical availability metadata without downloading or previewing content.

CID-only inputNo content previewGateway metadata

Results open in the detail view

The detail page runs the live availability check, then shows routing, gateway, timing, cache, and troubleshooting metadata in one place.

CID

Format validation

DHT

Provider lookup

HTTP

Gateway probe

What it is

A practical IPFS retrieval health check.

HiDHT is not a DHT crawler or content search engine. It is a focused diagnostic tool for answering a specific question: does this CID appear discoverable and retrievable from the public IPFS path right now?

IPFS publishing

Confirm that a newly published CID has routing signals and at least one working public gateway path.

NFT metadata

Check whether token metadata or media CIDs are reachable before pointing users to a collection.

Storage operations

Debug whether a retrieval issue looks like missing providers, gateway variance, or plain latency.

Team handoff

Share a neutral result page with engineers, support teams, or customers without exposing fetched content.

How it works

From CID to report in one flow.

The checker follows a fixed, conservative workflow so every result page is easy to compare and safe to share.

CID validation

Rejects URLs, magnet links, paths, raw hashes, and malformed identifiers before any network probe.

Provider discovery

Queries delegated routing providers and summarizes provider count plus a small peer sample.

Gateway retrieval

Tests public gateways with HEAD and one-byte ranged GET fallback, never full content downloads.

Troubleshooting

Explains what missing providers, gateway failures, or slow responses usually mean.

Reading results

A failed gateway is not the whole story.

IPFS retrieval depends on provider records, peer reachability, gateway policy, cache state, and latency. HiDHT separates those signals instead of flattening everything into a single pass/fail answer.

Status meanings

Available

Provider records exist and at least one public gateway returned a successful metadata response.

Partially available

Either routing or gateway retrieval is working, but not both. This often points to gateway variance or provider connectivity.

Not found / Error

The CID may not be announced, public gateways may not retrieve it, or an upstream routing endpoint may have timed out.

Safety boundaries

Metadata only. No preview. No proxy.

HiDHT never renders fetched IPFS content, never iframes gateway responses, and never provides a download button. The result page only shows technical availability metadata such as provider count, HTTP status, content type, and latency.

Read the docs

Monitoring demand

Need repeated CID checks?

The MVP collects monitoring requests from result pages. If enough users need scheduled checks, HiDHT will add alerts, history, webhooks, and status badges.

Run a check

Submit the CID once and review the generated detail report.

Request monitoring

Use the result page form to register interest in scheduled checks.

Validate demand

Monitoring will ship after real usage signals justify alerts and history.

Check CID