Your subdomain is covered by a wildcard certificate that already exists, so publishing is instant. A custom domain takes two DNS records and a wait for your provider — the certificate is our problem, not yours.
Add these two records at your registrar. We re-check on a backoff for up to seventy-two hours, and if it fails you are told which record was wrong rather than just that it didn't work.
| Type | Name | Value | TTL |
|---|---|---|---|
| TXT | _platform-verify | mv-8f3ac91e4b7d0625 | 300 |
| CNAME | alsafartravels.com | edge.musafy.in | 300 |
If your DNS is one we manage, we write both records for you from the dashboard.
Both records resolved. A certificate is requested automatically and the challenge is answered at the edge, so there is nothing to install and nothing to upload.
Your domain is now the primary one. The old subdomain redirects to it permanently, canonical links and the sitemap are rebuilt against the new host, and the routing cache is updated so the first visitor gets it right.
The wildcard certificate already covers every subdomain, so publishing on yourname.musafy.in is instant. Sell from it while your domain propagates.
Certificates are swept thirty days out and renewed without anyone being asked. An expired certificate on a travel site is a lost booking, so it is not left to a reminder.
Growth carries five custom domains and Scale twenty-five — one primary, the rest redirecting, each with its own certificate.
Pages are cached at the edge for five minutes and served stale while they refresh — and publishing an edit purges only your own pages, immediately.