Every domain where it belongs

The chain, per client

A client's online infrastructure is a fixed chain: domain, optionally a website, and the hosting it runs on. All three attach to the company and surface as panels on the client hub, so one page shows what sits where. Adding new attachable types (SSL, extra assets) is a module, not a rebuild of the client page.

• Domain: registrar, DNS provider, status and registry contact
• Website: on the root (@) or www, points at a hosting account
• Hosting: its own provider, IP address and a responsible owner

Registrar and provider, on the spot

Every domain points at a registrar and a DNS provider from your own catalogue; hosting points at its provider. If a name isn't there yet, you type it into the picker and create it on the spot (＋ add), without leaving the form. You curate the catalogue once under Instellingen, and everyone picks from it after that.

DNS that keeps itself current

For every domain a plain resolver reads public DNS: nameservers, DNSSEC and MX records. That works for every domain, not only the registrars we integrate with. A new domain is fetched right after you add it and refreshed daily after that, so the page stays right without anyone pressing refresh. An unreachable domain reads as "no data" and never breaks the rest of the batch.

• Nameservers, exactly as they resolve in public DNS
• DNSSEC: on, off, or not-yet-known
• MX records in priority order, so you see where mail goes

Websites with a technical owner

A domain gets at most one website, on the root (@) or on www, with a technical owner: your agency by default, or an outside party when a client runs it themselves. The website points at the hosting it runs on, so the whole chain from name to server lines up in one place. Hosting is its own entity too: shared infrastructure stays without a client rather than being forced onto one company.

Your fields, your trail

Domains, websites and hosting inherit your own extra fields, configurable per tenant, so whatever your agency tracks fits without custom code. Every change lands in the activity trail: who, what, when. It all runs under your brand, with your data under your control and cleanly separated per organisation, grouped in the navigation under "Hosting & domains".