An OAuth client can use the HTTPS URL of its Client ID Metadata Document as its client ID. Account Chief reads the document for the app name, redirect URIs, and authentication settings, allowing compatible clients to connect without a separately issued client ID.

Desktop and command-line OAuth clients can use a local HTTP callback on localhost, 127.0.0.1, or [::1]. Register the client as a native application; the callback port can vary during authorization, so the app can use an available local port.

The Domain Chief API now lets integrations list hosted DNS snapshots, inspect or export a saved zone, and create a named snapshot before a planned change. Preview a restore to see which records it would change, then restore the snapshot when needed.

Choose a date and time in your browser's timezone to load retained requests near that moment in the log stream. Browse earlier and later events for context, then return to the live stream when you are done.

FlowGuard now has an MCP endpoint at https://flowguard.network/mcp for compatible AI assistants. Connect it to inspect request logs, list the rules, actions, proxies and IP lists in your team, and investigate an event using its stream ID or surrounding log window.

OAuth clients can send a resource URI during authorization or device authorization to request a token for a specific API. Account Chief carries that audience through token exchange and refresh, and rejects a token request for a different resource.

For a domain using Domain Chief nameservers, open DNS Records → Manage zone → Scheduled changes to add, edit, or remove records at a chosen time. Review the planned changes before saving, and edit or cancel a pending schedule.

The new FlowGuard API lets you bring traffic investigations and protection changes into your own workflows. Query retained request logs, discover available log fields, list FlowGuard proxies and IP lists, and create or update rules and actions with scoped access.

Open DNS History from a hosted domain's DNS records to inspect saved versions of its zone. Domain Chief saves a snapshot before changes; you can also save a named snapshot before a planned migration.

Open DNS records, web redirect, and mail forwarding pages now update when another team member or a background operation changes the domain. You can follow record and forwarding changes without manually reloading the page.

Use the Domain Chief API's team event feed to keep a local copy of domains, contacts, DNS records, web redirects, and mail forwards current. Start with a checkpoint and initial snapshot, then follow a cursor and refresh resources named by change events.

Integrations can enable or disable mail forwarding, inspect setup status, manage aliases and destination addresses, and retry DNS verification through the Domain Chief API.

Team Owners can choose a role when inviting someone and change another member's role from Teams. Owner manages the team, Member uses connected apps, and Billing manages subscriptions and invoices without app access.

Integrations can now update team settings and manage membership through the Account Chief REST API. Invite or remove people, change a member's role, and list team access token metadata without exposing token values.

When creating a personal or team API token, you can choose Fine-grained permissions for apps that support them and select only the operations the token needs. Full access remains available when appropriate.

The Account Chief REST API now lets integrations list a team's connected apps, plans, and limits, and retrieve its invoices. Request invoice lines when you need a detailed billing report.

Integrations can preview and apply hosted DNS imports from BIND text or BIND, CSV, XLSX, and ODS uploads, choosing replace or merge. They can also export the full zone as BIND-compatible text.

Before changing a hosted DNS zone, review which records will be added, removed, or left unchanged. BIND, CSV, XLSX, and ODS imports can merge with existing records instead of replacing the full zone; TransIP imports and hosted-zone copies replace it.

The public homepage, domain search, features, and pricing pages are now available in Dutch. Use the language selector on these pages to switch between English and Nederlands; search links stay in the chosen language.

Search for, register, or transfer domain names containing supported non-ASCII characters. Domain Chief checks the selected TLD's allowed characters and converts eligible names to their canonical ASCII form for registry requests.