On July 7, 2026, I wrote an article about tagxx.vip.
I originally noticed this website because a college classmate told me he was actually using it. I subsequently checked some public pages and recorded the information I learned at the time along with my own thoughts.
Previous article:
However, when that article was published, I had not actually created an account myself yet.
Therefore, whether the registration entry could open normally, what the email verification process was like, which email addresses could be used for registration, and what the user backend looked like after registration were all actually unverified by me at the time.
On July 31, 2026, I decided to go ahead and complete this step.
This time, I used my phone connected to my home Wi-Fi in mainland China, and actually went through the entire registration and login process—from opening the website to creating an account, completing the login, and entering the user backend.
The registration was ultimately successful.
However, I also encountered a very specific issue during the process: I originally planned to register using a 163 email, but the current registration page does not support @163.com.
Below is a record of this actual operation process.
1. Opening tagxx.vip via home Wi-Fi
This test used a phone connected to my home Wi-Fi.
After opening the page, it did not immediately go to the homepage; instead, a black transit page appeared first:
Loading – Please Wait
The page also indicated that it would automatically redirect later.
After waiting a short while, the page completed the redirect normally and entered the TAGInternet page.


The brand name currently displayed on the actual page is TAGInternet.
Upon entering the homepage, you can see two entry points: “Register” and “Login”.
Therefore, I proceeded directly into the registration process.
2. The registration page opens normally
After entering the account page, you can switch between:
Login, Register, Reset Password
three functions.

After selecting “Register”, you can start creating a new account.
The main content required on the registration page includes the email address, email verification code, password, repeat password, and invitation code.
The invitation code is marked as an optional field.
I originally thought I would only need to enter an email, get a verification code, and set a password, but after actually operating it, I first encountered the first problem in this registration process.
3. 163 email cannot currently be used for registration
The first thing I filled in was one of my @163.com email addresses.
After entering it, the page directly prompted:
暂不支持 @163.com 邮箱
At this point, “Send Verification Code” could no longer operate normally.

The page also provided a “View supported emails” option below.
After expanding it, the email suffixes I actually saw this time included:
@qq.com, @gmail.com, @yahoo.com, @foxmail.com

There is a detail here worth noting.
The page prompted that it is not supported based on the email suffix before sending the verification code, rather than never receiving the email after sending the verification code.
Therefore, based on this actual behavior, it seems more like TAGInternet has currently set a support range for registration emails, rather than simply understanding it as “the 163 email cannot receive the verification code”.
As for why @163.com is temporarily not supported, the registration page itself did not provide an explanation.
It may involve email delivery, risk control, operational rules, or other technical reasons, but these are all just speculations for now, so I will not draw a conclusion on the specific cause at this time.
The email rules adopted by different services are also not the same.
For example, when I previously tested the Zoog registration process, the 163 email was usable. Therefore, @163.com itself is not unusable across all similar services.
I recorded the subsequent actual access testing of Zoog in the mainland China network environment and the official response in another article:
So, if you find that your email cannot be used when registering for tagxx.vip, you can first check the supported email range currently listed on the registration page, rather than waiting indefinitely for a verification code that was never actually sent.
It should be noted that this article records the page status actually seen on July 31, 2026.
If the range of supported emails changes in the future, the information displayed on the registration page at that time shall prevail.
4. Setting a password and confirming registration information
After resolving the email issue, the next step is to complete the email verification and set a login password.
Based on the information displayed on the registration page this time, the password needs to meet several basic requirements:
- At least 8 characters;
- Up to 32 characters;
- Include uppercase and lowercase letters, numbers, and special symbols;
- Pass the password strength check.
Once the password meets the requirements, the page will display a password strength indicator.
Below the registration page, there are also “Repeat Password” and “Invitation Code”.
The invitation code is an optional field.
Continuing further down, you can see the relevant terms and page prompts that need to be confirmed before registering.

During registration, I completed the confirmation according to the information provided on the page at the time, and then submitted the registration.
This part involves the platform’s own service rules, so this article will not provide additional explanation.
The relevant terms and page prompts may also change in the future, so when actually registering, you should still rely on the content provided on the page at that time.
5. Successfully completing registration
After completing the email verification, setting the password, and confirming the relevant information, I submitted the registration.
The account was ultimately created successfully.
In other words, based on this actual operation, the entire registration process can be completed end-to-end:
Open page → Enter registration page → Email verification → Set password → Submit registration → Create account.
The main problem I actually encountered was that the 163 email I originally planned to use was not within the current supported range.
Only after switching to an email supported by the page could the registration process continue.
6. Successfully entering the user backend after registration
After the account was created, I continued with the login test.
After logging in with the newly registered account, I successfully entered the TAGInternet user backend.

From the homepage, you can see entry points such as the Help Center, Personal Center, Invitation Rebate, and Online Customer Service, and the page also features functions like the Mall.
At this point, the registration and login process I intended to verify has been completed.
That is to say, in this test on July 31, 2026, I used my phone connected to my home Wi-Fi in mainland China to successfully complete the tagxx.vip / TAGInternet account registration and normally log into the user backend.
This is only the result I obtained in this actual environment, and it does not mean that the access situation in different regions, with different ISPs, or at other times in the future will necessarily be exactly the same.
7. What to watch out for during this registration process
After actually going through the entire process, the registration steps themselves are not complicated; what is really worth paying attention to in advance are actually a few minor issues that can easily get you stuck.
First is the email.
When I first used a 163 email, the registration page directly determined that it was currently unsupported, so it did not even enter the verification code sending stage.
If you encounter a similar situation, you can first expand “View supported emails” on the page to confirm whether the current email suffix is within the supported range.
Second is the password.
The registration page has a password strength check, so you can set a password that complies with the rules in one go according to the page prompts, avoiding repeated modifications.
Finally, there are the terms and related prompts on the registration page.
These contents may all change as the platform adjusts, so the screenshots in this article are mainly used to record this actual registration process, rather than serving as a long-term unchanging rule explanation.
8. tagxx.vip registration entry
If you plan to check the current registration page yourself, you can enter through the link below: tagxx.vip registration entry
9. How far this test went
My goal this time was mainly to verify the account registration and login process.
What has currently been actually completed is:
Entering the website → Opening the registration page → Creating an account → Logging in → Entering the user backend.
As for the subsequent plan selection, actual purchase, payment process, and post-purchase user experience, this article has not tested them yet, so it will not jump to conclusions in advance.
Compared to July 7, when I first only learned about it from public pages and classmate feedback, this time I have at least truly completed the registration and login phase.
At the same time, I also obtained a piece of information not present in the previous article:
The current tagxx.vip registration page does not support 163 emails, but the supported email types can be viewed directly from the registration page.
If I continue with a purchase later, I plan to continue recording the actual pages, operation process, and any issues encountered in this manner, rather than judging solely based on product descriptions.
需要长期技术维护或远程问题排查?
我是拥有 15+ 年经验的 PHP / Go 后端工程师,长期关注已有系统维护、Bug 修复、性能优化、服务器排查、WordPress 网站维护和小功能迭代。
如果你的项目遇到以下情况,可以先从一次小问题排查开始合作:
- ✅ PHP / Laravel / Yii2 老项目无人维护
- ✅ Go / Gin 后端接口需要排查或优化
- ✅ WordPress 网站访问慢、报错或插件冲突
- ✅ Nginx / MySQL / Redis / Linux 服务器异常
- ✅ CDN / Cloudflare / DNS / HTTPS 配置问题
- ✅ 需要长期远程技术支持或兼职维护
更多介绍请查看:关于我 & 合作
微信:13980074657
邮箱:shuijingwanwq@gmail.com
Telegram:@shuijingwan
GitHub:https://github.com/shuijingwan


发表回复