Frequently asked questions

What is this?

A public DC hublist directory. It periodically verifies each listed hub and publishes the live list for DC clients.

How do clients use it?

Add /hublist.xml.bz2 (or /hublist.xml) to your client's hublist sources. A machine-readable /hublist.json and an /rss feed are also available.

How do I register a hub?

Easiest: use the Add your hub form. Or send an HTTP GET to /register?address=<hub url>&name=<name>&description=<text> (adc:// adcs:// dchub:// nmdcs://). NMDC hub software may instead use classic hublist registration on port 2501. New hubs are pinger-verified and reviewed before listing.

Why is my hub not listed?

It must be reachable by our pinger and, for anti-hijack, its address should resolve to the registrant's IP. Hubs that fail repeatedly are marked offline and eventually dropped.

What does [KP] mean?

The hub presented a TLS certificate whose keyprint we pinned; the published adcs:// address carries ?kp=SHA256/... so clients can verify it. If a hub later presents a different keyprint we pause it and record it on /security.

Is there an API?

Yes: /api/hubs returns JSON and accepts filters — ?country=RU&minusers=10&proto=adcs&kp=1&ipv6=1&limit=100 (CORS-open). Full dumps are at /hublist.json and /rss; live network trends at /health. Hub owners can embed a live status badge with <iframe src="/embed?id=<hub id>">.

Can I get a filtered list?

Yes — see /lists for ready-made sub-lists (ADC-only, secure-only, per-country), or add the same filters to the XML: /hublist.xml?country=RU&proto=adcs&minusers=10.

I registered a hub — how do I manage it?

The registration response returns a one-time Owner-Token. Keep it; it lets you edit your hub's description or request delisting at /owner?token=... without contacting the operator.