Generated 2026-06-11 03:00:17 UTC · 3 known nodes · feed.json carries the raw signed wires for independent re-verification.

Federation topology · heartbeat-discovery, not message traffic

CLdnsmesh.pro0.7.5DEdnsmesh.de0.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.1166 ms14 ms2 ms
Google 8.8.8.8192 ms40 ms164 ms
Quad9 9.9.9.9485 ms96 ms371 ms
OpenDNS 208.67.222.222283 ms49 ms323 ms
Comodo 8.26.56.26empty answerempty answerempty answer
Level3 4.2.2.1496 msempty answer503 ms
Hurricane Electric 74.82.42.42empty answer6538 ms1713 ms
Verisign 64.6.64.6335 ms32 ms395 ms
AdGuard 94.140.14.14989 ms544 ms852 ms
Yandex 77.88.8.8425 ms670 ms811 ms
Alibaba 223.5.5.5245 ms603 ms595 ms
DNSPod 119.29.29.29470 ms506 ms502 ms
KT Korea 168.126.63.1634 ms500 ms768 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.pro

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

https://dnsmesh.de

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

https://dnsmesh.io

Status4m 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.