Skip to main content

đŸ§” Fixing a stuck custom domain verification due to TXT record spacing

Explains why a stray space in a TXT record value can silently break custom domain verification and how to fix it.

🔍 Why Verification Can Get Stuck

When you set up a custom domain, you need to add a TXT record with a specific value at your domain provider. This value must match exactly, character for character.

Even a tiny difference, like a space at the start or end of the value, will cause verification to fail. The record can look completely correct on screen and still not match.

👀 Why You Might Not Notice the Problem

Extra spaces before or after the TXT value are invisible when you're looking at the record in your domain provider's dashboard. There's no visual clue that anything is wrong, so it's easy to assume the record is fine when it isn't.

If your verification has been pending for a while and doesn't seem to be moving forward, a spacing issue is one of the most common causes.

✅ How to Fix It

If verification is stuck, don't just wait longer. Waiting won't help if the value itself doesn't match.

  1. Go back to the TXT record setup instructions and copy the required value again.

  2. Open the TXT record in your domain provider's dashboard and carefully check the value field.

  3. Delete the existing value completely and paste in the required value fresh, making sure there are no spaces before or after it.

  4. Save the record and allow verification to run again.

Re-checking and correcting the exact value is the fix, not extra waiting time, and once it's right, verification usually completes quickly!

If you get stuck, message us from the chat bubble and we'll help you sort it out in no time!

Did this answer your question?