Skip to content
FeaturesPricingAffiliateBlogHelpAboutContact
Get StartedSign In
Back to Blog
industry2026-05-236 min read

Domain verification has been stuck for three weeks — does your POST and your verifier agree on the CNAME?

A hotel owner in Aydın had been stuck on custom domain verification for 3 weeks. The DNS was correct — the bug was in setup: POST response said `dns_instructions.value = "thmenu.com"` but the verifier expected `menu.thmenu.com`. Doc-vs-code drift since launch. PR #570 UU F2 fix.

th

thMenu Team

thmenu.com

Found this helpful? Share it.

Related articles

✦📈
industry

Why Digital Menus Increase Restaurant Revenue by Up to 30%

Studies show restaurants using digital QR menus see measurable increases in aver…

✦🔻
industry

When a Customer Downgrades, What Happens to Old Features? — The Silent Feature-Drift Problem in SaaS

Most SaaS apps run a single line of code when a customer downgrades — but old fe…

✦🛡️
industry

JWT alg-confusion attack — why Supabase's HS256 → RS256/JWKS migration breaks legacy verifiers

Verifiers that never decode the JWT header are wide open to `alg=none` and alg-c…