Verification keeps failing.

Question

Verification keeps failing.

Thor Network Inc 0

Verification of website thornetwork.io despite providing purchase reciept from namecheap.

Prabhavathi Manchala 2,315 Reputation points Microsoft External Staff Moderator

2025-06-25T12:55:37.33+00:00
Hi Thor Network Inc,

You're trying to verify ownership of your custom domain thornetwork.io in Azure, but the verification keeps failing even after providing the Namecheap purchase receipt. You've correctly purchased the domain, are attempting to connect it to an Azure service (like App Service, Static Web App, or Front Door) and have tried verifying it without success.

Azure doesn't verify domain ownership using a purchase receipt; instead, it requires DNS based verification to confirm control of the domain typically by adding a TXT or CNAME record to your domain's DNS settings, depending on the service. If this record is missing, incorrect, or hasn’t fully propagated, the verification will keep failing even if the domain has been purchased.

Sign in to Namecheap where you manage your DNS.

Go to the Advanced DNS section for thornetwork.io.

In Azure (App Service or wherever you're trying to verify), you should see a TXT record that looks like:

Name/Host: asuid.thornetwork.io Type: TXT Value: [unique-code-from-Azure]

Copy this record and add it in Namecheap exactly as shown.

Save the DNS changes and wait 10–15 minutes (DNS propagation time).

Go back to Azure and click Verify again.

Azure App Service Custom Domain Setup

Azure Static Web Apps Custom Domain

Make sure the TXT record is correct and not repeated. Use dnschecker.org to check if it's showing globally. Once Azure finds it, the verification will work.

1 answer

Your answer

Prabhavathi Manchala 2,315 Reputation points Microsoft External Staff Moderator

2025-06-25T12:55:37.33+00:00

Hi Thor Network Inc,

You're trying to verify ownership of your custom domain thornetwork.io in Azure, but the verification keeps failing even after providing the Namecheap purchase receipt. You've correctly purchased the domain, are attempting to connect it to an Azure service (like App Service, Static Web App, or Front Door) and have tried verifying it without success.

Azure doesn't verify domain ownership using a purchase receipt; instead, it requires DNS based verification to confirm control of the domain typically by adding a TXT or CNAME record to your domain's DNS settings, depending on the service. If this record is missing, incorrect, or hasn’t fully propagated, the verification will keep failing even if the domain has been purchased.

Sign in to Namecheap where you manage your DNS.

Go to the Advanced DNS section for thornetwork.io.

In Azure (App Service or wherever you're trying to verify), you should see a TXT record that looks like:

Name/Host: asuid.thornetwork.io Type: TXT Value: [unique-code-from-Azure]

Copy this record and add it in Namecheap exactly as shown.

Save the DNS changes and wait 10–15 minutes (DNS propagation time).

Go back to Azure and click Verify again.

Azure App Service Custom Domain Setup

Azure Static Web Apps Custom Domain

Make sure the TXT record is correct and not repeated. Use dnschecker.org to check if it's showing globally. Once Azure finds it, the verification will work.

Answer 1

Hi, in Azure, the domain purchase receipt is useless: the only proof of ownership is the DNS record. Until you create the TXT record (and, for root domains, also the A-record) required by Azure and visible publicly, the Verify button will always fail.

For root domains (e.g. thornetwork.io), Azure looks for:

a TXT record with host asuid and exact value copied from the portal;

an A record pointing to the App Service IP.

For subdomains (e.g. www.thornetwork.io), you need:

a TXT record with host asuid.www (or _dnsauth.www for Static Web Apps);

a CNAME record from www to your .azurewebsites.net.

To add them in Namecheap: go to Advanced DNS, create a TXT record (asuid or asuid.www) with the value copied from Azure, automatic TTL, then also add the A record (for the root) or CNAME (for the sub). Save everything, wait a bit (usually a few minutes), then go back to Azure and press Verify.

You can check if the record is visible with nslookup -type=TXT asuid.thornetwork.io or tools like whatismydns.net.

Common problems:

The record is there but Azure does not see it: disable proxy/forwarding (e.g. on Cloudflare).

The host field in Namecheap is wrong: write only asuid, not thornetwork.io.asuid.

After 1h still nothing: clear the DNS cache (ipconfig /flushdns) or test from outside.

Share via

Verification keeps failing.

1 answer

Your answer