Generated 2026-07-28 10:03:23 UTC · 3 known nodes · feed.json carries the raw signed wires for independent re-verification.

Federation topology · heartbeat-discovery, not message traffic

DEdnsmesh.de0.7.5CLdnsmesh.pro0.7.5USdnsmesh.io0.7.5

An arrow from A → B means A's seen-graph (_dnsmesh-seen.<A-zone>) carries a verified heartbeat from B. This is the federation discovery view — who has heard from whom over the public DNS chain. Message traffic is private (E2E encrypted) and is NOT shown here.

Public-resolver reachability · can major resolvers find these nodes?

Resolverdmp.dnsmesh.dedmp.dnsmesh.iodmp.dnsmesh.pro
Cloudflare 1.1.1.1122 ms113 ms163 ms
Google 8.8.8.8118 ms158 ms143 ms
Quad9 9.9.9.9112 ms287 ms296 ms
OpenDNS 208.67.222.222260 ms208 ms253 ms
Comodo 8.26.56.26263 ms170 ms481 ms
Level3 4.2.2.1323 ms234 ms358 ms
Hurricane Electric 74.82.42.42137 ms147 ms202 ms
Verisign 64.6.64.6297 ms161 ms274 ms
AdGuard 94.140.14.14614 ms179 ms390 ms
Yandex 77.88.8.8366 ms636 ms866 ms
Alibaba 223.5.5.5141 ms258 msanswer did not verify
DNSPod 119.29.29.29521 ms369 ms503 ms
KT Korea 168.126.63.1727 ms666 ms724 ms

Tested at build time from a GitHub Actions runner: each row is a curated public DNS resolver, each column is a node. A green cell means the resolver answered _dnsmesh-heartbeat.<zone> with a wire that verifies under Ed25519. Your client can do the same lookup with the same result. The list is illustrative — every internet-connected DNS resolver can perform the same query.

Known nodes · geo + hosting

https://dnsmesh.de

Status19s ago
Version0.7.5
Operator keyfbe50814…cdd9
HostingHetzner
RegionNuremberg, Bavaria, Germany
IP178.104.241.208
Heard viadmp.dnsmesh.de

https://dnsmesh.pro

Status1m ago
Version0.7.5
Operator key55dd5085…bfef
HostingOPENCLOUD SpA
RegionCuricó, Maule Region, Chile
IP45.7.229.112
Heard viadmp.dnsmesh.pro, dmp.dnsmesh.de

https://dnsmesh.io

Status3m ago
Version0.7.5
Operator keyc0e5385e…32c2
HostingDigitalOcean, LLC
RegionSanta Clara, California, United States
IP24.199.107.165
Heard viadmp.dnsmesh.io, dmp.dnsmesh.pro, dmp.dnsmesh.de

Geo and ASN data via ip-api.com lookup at build time. Each node is the same self-signed HeartbeatRecord wire that lives at _dnsmesh-heartbeat.<zone> on the public DNS chain — the geo block is descriptive metadata for humans and is NOT signed.