IPFS Check

Check the retrievability of data by CID

Paste in a Content ID and the multiaddr (optional) of a host to check if it is expected to be retrievable

CID or multihash Multiaddr (optional)

Backend Config

Backend URL IPNI Indexer

Check Timeout (seconds) 60

Raw Output

Where do I find my multiaddr?

Using IPFS Desktop or IPFS WebUI
- Open the IPFS WebUI "Status" page via the IPFS Desktop menu or by visiting "http://127.0.0.1:5001/webui" (when using the default config settings)
- If you want to test your peerID rather than a particular address enter /p2p/{YourPeerID}
- If you want to test a particular address then click the "Advanced" dropdown to see the node's addresses
Using the kubo CLI
- If you want to test your peerID rather than a particular address run ipfs id and enter /p2p/{YourPeerID}
- If you want to test a particular address then choose an entry from the list of addresses output by ipfs id

Could not connect to the multiaddr. Machines on the internet cannot talk to your machine. Fix your firewall, add port forwarding, or use a relay.
Could not find address in the dht. Your machine is either not connected to the IPFS Public DHT (even as a client), or is not advertising the address that you are testing with. As a result no one will be able to contact you on that address if they only learn about your peerID, as is the case for content advertised in the IPFS Public DHT
Multihash not advertised in the dht. Your machine has not advertised that it has the given content in the IPFS Public DHT. This means that other machines will have to discover that you have the content in some other way (e.g. pre-connecting to you optimistically, pre-connecting to you since related content is already advertised by you, some rendezvous service, being on the same LAN, etc.). If using kubo consider enabling the Accelerated DHT Client, which will advertise content faster and in particular should enable you to continue to republish your advertisements every 24hrs as required by the network.
Peer has not responded that it has the CID. Your node does not think it has the data you think it does, or it took too long to respond. Until this is resolved other machines will be unable to download that content from you.