Domain Verification Debugging
These are some errors that might be encountered while verifying a domain along with debugging steps you should take when encountering the error message.
A domain can only contain characters, numbers, and hyphens. The hyphen cannot be the first or last character. For example,
face-book.com are valid domains. Domains do not include slashes.
https://facebook.com are invalid domains.
You can also verify a subdomain. For example,
www.facebook.com is a subdomain of
facebook.com. When you verify a domain, you also get control of all subdomains, so we recommend that you verify the top-level domain (in this case,
Another Business Manager account has already verified the domain. If there are other Business Manager accounts that might have access to the domain, reach out to those accounts and request that the business shares the domain with your account. This error can also occur if the domain has changed owners and the old owners verified the domain in their Business Manager account. Contact support for additional help.
We weren't able to successfully retrieve the DNS TXT records. Try to verify the domain again. If you still encounter issues, contact support.
We did not find the verification file at the root of your domain. Double check that you have uploaded the file to the correct location.
We require that the file is uploaded to the root of your domain. Verification fails if we are redirected to another location when we try to find the verification file. We do allow redirects from a top-level domain to the
www subdomain. For example, if you are trying to verify
mydomain.com, you can redirect us to
www.mydomain.com/verificationfilename.html. We also allow redirects between
The contents of the HTML verification file did not exactly match the verification code provided. Make sure that there is no other text or HTML markup on the webpage. You can double check by right-clicking and selecting View Page Source.