Nimriz

DNS verification

How verification works, provider-specific record instructions, and what to check when stuck.

Why DNS verification is required

DNS verification proves that you are the authorized owner of the hostname you want to use as a Nimriz short-link domain. Without this step, anyone could claim your branded domain and create links that appear to originate from your brand.

Verification is a one-time step per domain. Once verified, you do not need to repeat it unless the verification record is removed from your DNS.

What you are publishing

Nimriz generates a unique TXT record for each domain you add. You publish this record at your DNS provider to demonstrate control. The record looks like:

Type:  TXT
Name:  _nimriz-verify.links.example.com
Value: nimriz-verify=<unique-token>

The Name field is always a subdomain of your hostname prefixed with _nimriz-verify.. The Value field is a unique opaque token Nimriz generates when you add the domain. Both values are shown in your dashboard-copy them exactly.

Step-by-step verification

  1. Copy the record details from your Nimriz dashboard (Settings → Domains → your domain → the TXT record shown).
  2. Log in to your DNS provider-this is wherever you manage DNS for the domain (e.g., Cloudflare, Route53, GoDaddy, Namecheap, Hover, or your web host's DNS panel).
  3. Create a new TXT record with the Name and Value from step 1.
  4. Save the record at your DNS provider.
  5. Return to Nimriz and click Verify now on your domain.

Nimriz queries DNS for the record and confirms ownership when it is found. If the check succeeds, the domain moves to Verified status.

How to enter the record at common providers

Cloudflare

  1. Go to your Cloudflare dashboard → DNS → Records.
  2. Click Add record.
  3. Set Type to TXT.
  4. Enter the Name exactly as shown. Cloudflare automatically appends your root domain, so if the full name is _nimriz-verify.links.example.com and your domain in Cloudflare is example.com, enter just _nimriz-verify.links.
  5. Paste the Value from Nimriz into the Content field.
  6. Set TTL to Auto.
  7. Make sure the Proxy status is DNS only (grey cloud icon)-TXT records cannot be proxied.
  8. Click Save.

AWS Route 53

  1. Go to Route 53 → Hosted zones → your domain.
  2. Click Create record.
  3. Enter the subdomain part in the Record name field (e.g., _nimriz-verify.links if your short domain is links.example.com).
  4. Select type TXT.
  5. Paste the Value into the Value field, enclosed in double quotes: "nimriz-verify=<token>". Route 53 requires TXT record values to be quoted.
  6. Click Create records.

GoDaddy

  1. Log in to GoDaddy → My Products → DNS.
  2. Click Add under DNS Records.
  3. Select TXT as the record type.
  4. In the Host field, enter the subdomain prefix only (e.g., _nimriz-verify.links for a links.example.com hostname, since GoDaddy appends the root domain automatically).
  5. Paste the Value from Nimriz.
  6. Set TTL to 600 (10 minutes) or lower for faster propagation.
  7. Click Save.

Namecheap

  1. Log in to Namecheap → Domain List → Manage → Advanced DNS.
  2. Click Add New Record.
  3. Select TXT Record.
  4. Enter the Host as the subdomain portion only, without the root domain (e.g., _nimriz-verify.links).
  5. Paste the Value from Nimriz.
  6. Set TTL to automatic.
  7. Click the checkmark to save.

How long propagation takes

DNS changes take time to spread across the global DNS infrastructure. The time depends on:

  • Your DNS provider's processing speed (usually seconds to minutes).
  • The TTL (Time to Live) of the record-lower values mean faster propagation.
  • Upstream caching by DNS resolvers around the world.

Most records propagate within 5–15 minutes. In some cases it can take up to a few hours. If verification is still failing after an hour, proceed to the troubleshooting steps below.

You can check whether your record is visible using a DNS lookup tool:

dig TXT _nimriz-verify.links.example.com

Or use an online tool like dnschecker.org to see the record from multiple global locations.

Triggering a manual re-check

If you believe your DNS record is live but the domain is still showing Pending, you can manually trigger a re-check:

  1. Go to Settings → Domains in your Nimriz dashboard.
  2. Find the domain showing Pending status.
  3. Click Verify now (or the check/retry icon next to the domain).

Nimriz will immediately query DNS again. If the record is found, the domain transitions to Verified.

After verification: what happens next

Verification confirms ownership. After that, Nimriz also needs to activate routing for your hostname at the Cloudflare edge before redirects go live. This activation (which provisions SSL and routes traffic) happens automatically and typically completes within a few minutes of verification.

The domain reaches Ready status once both steps are complete. Your domain is ready for link creation and live traffic only when it shows Ready-not just Verified.

Troubleshooting

Verification fails even after adding the record

  • Check the exact record name. The most common mistake is publishing the record on the root domain instead of the specific subdomain. If your short-link hostname is links.example.com, the TXT record name must be _nimriz-verify.links.example.com, not _nimriz-verify.example.com.
  • Check for extra spaces or invisible characters in the Value field. Copy directly from the Nimriz dashboard-do not retype manually.
  • If you are using Cloudflare, confirm the record is set to DNS only (grey cloud). Proxied records are not visible to external DNS queries.

Verification succeeds but the domain never reaches Ready

  • Confirm the CNAME record is also published (pointing your hostname to Nimriz's edge). Verification only confirms ownership-traffic routing requires the CNAME.
  • If the CNAME is present and propagated but the domain is still not Ready after 30 minutes, contact support with your domain name and workspace ID.

The verification record was removed accidentally

Re-add the TXT record at your DNS provider. Nimriz will re-verify the next time you click Verify now or on the next automatic check cycle. The domain will return to Ready status once verification and edge activation complete again.

Related guides