Inside Bitcoin
Opening the selected file…
Inside Bitcoin
Opening the selected file…
The code behind the network, with room to understand it.
Release published 2026-10-28 · Snapshot fetched 2026-11-01. Latest stable release at fetch time; development branches and Git history are excluded. Only the selected code window and visible folders load here.
1Expectations for DNS Seed operators2====================================4Bitcoin Core attempts to minimize the level of trust in DNS seeds,5but DNS seeds still pose a small amount of risk for the network.6As such, DNS seeds must be run by entities which have some minimum7level of trust within the Bitcoin community.9Other implementations of Bitcoin software may also use the same10seeds and may be more exposed. In light of this exposure, this11document establishes some basic expectations for operating dnsseeds.130. A DNS seed operating organization or person is expected to follow good14host security practices, maintain control of applicable infrastructure,15and not sell or transfer control of the DNS seed. Any hosting services16contracted by the operator are equally expected to uphold these expectations.181. The DNS seed results must consist exclusively of fairly selected and19functioning Bitcoin nodes from the public network to the best of the20operator's understanding and capability.222. For the avoidance of doubt, the results may be randomized but must not23single-out any group of hosts to receive different results unless due to an24urgent technical necessity and disclosed.263. The results may not be served with a DNS TTL of less than one minute.284. Any logging of DNS queries should be only that which is necessary29for the operation of the service or urgent health of the Bitcoin30network and must not be retained longer than necessary nor disclosed31to any third party.335. Information gathered as a result of the operators node-spidering34(not from DNS queries) may be freely published or retained, but only35if this data was not made more complete by biasing node connectivity36(a violation of expectation (1)).386. Operators are encouraged, but not required, to publicly document the39details of their operating practices.417. A reachable email contact address must be published for inquiries42related to the DNS seed operation.44If these expectations cannot be satisfied the operator should45discontinue providing services and contact the active Bitcoin46Core development team as well as posting on47[bitcoin-dev](https://groups.google.com/g/bitcoindev).49Behavior outside of these expectations may be reasonable in some50situations but should be discussed in public in advance.52See also53----------54- [bitcoin-seeder](https://github.com/sipa/bitcoin-seeder) is a reference implementation of a DNS seed.
Independent explanations by MyBitcoinExplorer. Not affiliated with or endorsed by Bitcoin Core. Guides are educational and do not replace the source or its tests.
Bitcoin Core source © its contributors, distributed under the MIT license. Original notices and bundled third-party licenses are retained in the source tree.