Why is my custom domain verification pending?

Keep your working Tapmy URL live and avoid deleting or swapping records over and over while you work this out. Exact records and timing are not stated here, because they come from your own domain screen.

What should I gather first?

Collect the domain and host you want, the records Tapmy shows, your DNS provider, the real nameservers, when you last changed anything (with time zone), the TTL, any proxy or CDN setting, and a public lookup result. Keep the previous working setup safe.

How do I find out why verification is pending?

Four things must work in turn: public DNS, Tapmy's ownership check, routing, and the TLS certificate. Passing one does not mean the next is done.

1. Check the domain was added to the right Tapmy store, and copy the current records from that store's domain screen.
2. Find the authoritative nameservers. Make sure you edited the active DNS zone and not an unused registrar or old provider.
3. Compare each record's type, exact host and value with a public lookup. Watch for hidden suffixes, doubled labels, spaces and quotes.
4. Look for conflicting A, AAAA or CNAME records or forwarding rules on the same host. Do not delete one until you know who owns it and how to undo it.
5. If a DNS proxy or CDN is on, check whether Tapmy expects direct verification. Change it only if your instructions say so.
6. Allow for cached answers based on the old TTL. Do not promise a set wait, and do not keep editing in the same window.
7. Once public DNS matches, retry verification with the supported button and note the response and time.
8. If DNS matches but a browser shows a privacy or certificate warning, stop sharing the URL and contact Support with evidence.

How do I know it is done?

Public DNS matches your instructions, Tapmy marks the domain verified, the host loads your store with valid HTTPS, and the Tapmy and custom URLs do not loop. Your email still works. Test with made-up data and check the result in Tapmy and at your provider.

Why is it still pending with matching DNS?

• Pending although DNS matches. Re-check the exact host, the provider that really hosts DNS, proxy state, when you last changed it, and whether the verification value was regenerated.
• Root domain works but www fails. Both hosts may need their own supported records or a redirect. Do not guess the pattern.
• The old site still appears. Check delegation, forwarding, resolver cache and CDN, and test from another network.

No propagation or certificate time is guaranteed, and custom-domain plan rules are not covered here. Never tell anyone to delete email, ownership or security records as a general fix.

Make one reversible change at a time. Never share passwords, codes, API keys, tokens or DNS login details.

What should I do after it verifies?

Test root and www, phone and desktop, redirects, HTTPS, checkout and analytics, and know how to roll back, before you replace your Tapmy URL everywhere. For record basics, see DNS records explained.

If it still fails, contact Tapmy Support with the store, provider, public host, time and time zone, exact error, expected result and screenshots. Rotate any exposed credentials at the provider first.