tuvi.akivn.net now redirects 301 to tuvi.akinet.me
tuvi.akivn.net switched from a static moved notice to a real 301 redirect for all traffic, with a self-unregistering service worker clearing old caches.
The old domain tuvi.akivn.net (Firebase Hosting, project akinet-e7327, site tuviaki) has just moved from a static "we moved" notice, live since 2026-07-26, to a real 301 redirect for all traffic, pointing to tuvi.akinet.me. Checking the live domain with curl -I after deploy shows every route returning a genuine 301, not a preview result.
Where does tuvi.akivn.net redirect to?
Eight old routes map 1:1 to their tuvi.akinet.me equivalents:
- ◆
/→https://tuvi.akinet.me/ - ◆
/gioi-thieu.html→/about - ◆
/lien-he.html→/contact - ◆
/minh-triet.html→/minh-triet - ◆
/vi-nhan.html→/vi-nhan - ◆
/uikit.html→/uikit - ◆
/luan.htmland every old essay under/luan/*.html→/luan - ◆
/tai-khoan.html→/me
Why replace the service worker too?
The old tuvi.akivn.net ran a Workbox precache-first service worker: it cached content on the first visit and served from cache afterwards. Leaving it in place would mean returning visitors keep getting stale cached content and never reach the new 301 redirect, so changing the server route alone is not enough. /sw.js is now a self-unregistering "kill-switch" service worker: when it activates, it wipes every cache, unregisters itself with unregister(), and reloads the open tabs. Only after that does the next request reach the server and pick up the redirect.
A migration, not a sunset
This is not a shutdown: tuvi.akivn.net has not disappeared, it has become a 301 bridge to the official domain, like the ecosystem's app.akivn.net 301 redirect to app.akinet.me on 2026-07-11. The full Tử Vi Đẩu Số experience now lives at one address: tuvi.akinet.me.
The shared Aki account still signs in at the new home, but charts saved on the old build were not carried over, so they must be cast again.