Lockally

      Use your API key in the examples

      Replaces lk_live_… in the code samples on this site so you can copy and run them. It is stored in this browser only and is never sent anywhere, including to Ask AI.

      It will be visible on the page. Use a test key if you are sharing your screen or taking screenshots.

      Configure automatically

      Publishing six DNS records by hand is where most domain setups go wrong: a record at the apex instead of a subdomain, a token wrapped in a prefix, a truncated key. Domain Connect removes that step where your DNS provider supports it.

      You are redirected to your provider, you approve, and the records are written into your zone for you.

      GET /v1/domains/{domain}/dns-connect        scope: domains:read

      Ask per domain, do not guess

      The endpoint performs live discovery against the domain’s own DNS provider, so you never have to maintain a list of who supports what:

      {
        "enabled": true,
        "supported": true,
        "provider_name": "IONOS",
        "apply_url": "https://domainconnect.ionos.com/...",
        "control_panel_url": "https://..."
      }
      Field
      enabled whether this server offers the feature at all
      supported whether this domain’s provider advertises Domain Connect
      provider_name a friendly label, for your UI
      apply_url open this in a browser; the provider writes the records
      control_panel_url the provider’s manual DNS editor, as a fallback
      reason why it is unsupported, when it is

      Discovery costs a DNS lookup or two, so it is not instant. Pass ?probe=1 to ask only “is the feature on here” without the lookups, which is what you want on page load before deciding whether to show a button.

      What it writes

      The same records POST /v1/domains returns: verification, SPF, DKIM, MX and DMARC. Requests are signed (RS256) so the provider can verify they genuinely came from Lockally rather than from somebody who guessed the URL.

      You still have to verify. Domain Connect publishes the records; it does not tell us they are there. Call POST /v1/domains/{domain}/verify afterwards, and allow for DNS propagation as usual.

      When it is not supported

      "supported": false is the common case, and it is not a problem: it means your provider does not advertise the protocol, so you publish the records yourself. Use control_panel_url to send people straight to the right page of their provider’s editor.

      Support is the provider’s decision, not ours, and it changes. IONOS carries the Lockally template today. Several large registrars do not offer the protocol at all, or no longer offer it on standard plans, so treat supported as the answer rather than assuming from the provider’s name.

      Nothing is lost by publishing by hand. The automatic path saves typing; it does not unlock anything.