Domain Connect Link

Generate signed setup links from provider settings and DNS template parameters to test Domain Connect integration.

Credits
Start with discovery to fetch Domain Connect endpoints, then confirm the service provider ID, private key, and template parameters.

About Domain Connect Link

Generate a signed Domain Connect apply URL from provider settings and template parameters. Inspect the canonical query while debugging a provider integration before opening its authorization flow.

How to use Domain Connect Link

  1. Supply provider settings, template identifiers and parameter values.
  2. Enter the signing key and generate the apply link.
  3. Inspect the canonical query and test the link with the intended provider.

Input and output example

Input and settings
Provider settings + template parameters + signing key
Expected output
Signed apply URL and the canonical query used for signing.

When to use this tool

  • Debug parameter encoding and signature mismatches.
  • Validate a Domain Connect integration in a test environment.

Limits to know before using it

A generated link does not apply DNS changes by itself. Provider templates and published verification keys must match your configuration.

Data handling and cost

Settings, parameters and the private key are sent to the server for signing. The asynchronous job workflow stores the submitted input and results; do not assume immediate deletion. Use a dedicated test key and review the site privacy policy before submitting secrets.

Each successful run uses 1 credit. Guest trials depend on your available allowance; register or sign in when it runs out. Failed jobs follow the service refund rules.

Frequently Asked Questions

Yes. Signing runs on the server. Submitted job input, including the private key, is persisted by the asynchronous job workflow. Do not assume immediate deletion; use a dedicated test key and review the privacy policy.

The Domain Connect spec requires parameters to be sorted alphabetically and URL-encoded in a specific way before signing. The canonical query shown in the result is the exact string that was signed, useful for debugging signature mismatches.

No. The tool generates the signed apply URL but does not follow it. The URL must be opened by the end user in their browser to trigger the DNS provider's authorization flow.

Related Tools