Account & Authentication
Learn about AniBT account registration, email OTP sign-in, password recovery, and session lifecycle.
AniBT provides modern email OTP and session authentication to support anime tracking and fansub workflows.
Browsing releases, downloading .torrent files, copying magnet links, and subscribing to public RSS feeds do not require an account. Registration is only needed if you want to follow anime, use private merged RSS feeds, or publish releases as a fansub group member.
Quick Links
- Register New Account: anibt.net/auth/sign-up
- Sign In to Account: anibt.net/auth/sign-in
Registration domains and email limits
New email registrations accept these exact domains, excluding their subdomains:
qq.com, foxmail.com, 163.com, 126.com, yeah.net, gmail.com, googlemail.com, outlook.com, hotmail.com, live.com, msn.com, icloud.com, me.com, mac.com, yahoo.com, yahoo.co.jp, proton.me, protonmail.com, pm.me, fastmail.com, sina.com, sina.cn, sohu.com, aliyun.com, 139.com, 189.cn.
Existing accounts can still verify their original address and reset their password, including addresses on custom domains outside this list. Third-party sign-in is unaffected.
- Requests for the same mailbox must be at least 60 seconds apart, with at most 5 in any rolling 24-hour period. Registration, verification and password-reset requests share this allowance.
- Of those 5, requests without proof can take at most 3 in total, and at most 2 of them can come from one source; the remaining 2 or more are kept for requests with proof. A request has proof when it passed the bot verification (requesting a sign-up code, "Forgot password", or "Set Password" in your profile) or when the account that owns the address sends it while signed in. Everything else has no proof, for example a send from the email verification page, or a sign-up resend within 10 minutes that skips the bot verification. So someone else can use up at most 3 of your requests, and you still receive mail after passing the bot verification or signing in.
- A source (an IPv4 address, or the /64 network of an IPv6 address) can make at most 10 eligible email requests in any rolling hour. People sharing an office, school or home network may share this allowance.
- Gmail dot variants, plus aliases and
googlemail.comshare one allowance without changing the account address. - Wait before retrying a limited request. A rejected resend does not invalidate the previously sent code; expired or already used codes remain invalid.
- A wrong code, an expired code, and a code whose 5 attempts are used up all show "Wrong or expired code. If it keeps failing, request a new one". If it keeps failing, request a new code.
- Failed or unconfirmed sends can still consume the allowance. The success message comes back before the email is sent, so it does not confirm that an email was sent or delivered.
- Emails use the language of the page you sent the request from: English pages (
/en/…) send English, Traditional Chinese pages (/zh-hant/…) send Traditional Chinese, and every other page sends Simplified Chinese.
Registration Steps
Request Email Verification Code
Enter your active email address on the sign-up page and pass the bot verification. The system will send a 6-digit verification code to your inbox, valid for 10 minutes.
Fill In Profile Information
Enter your desired nickname, password, and the 6-digit code received, then submit to create your account. A password must be 8–128 characters long; the form tells you right away when it is outside that range. Resetting and changing a password follow the same rule.
Automatic Sign-In
Upon successful registration, you will be automatically signed in. If the process is interrupted, retry in the same browser tab without reusing an expired or consumed verification code.
Verification code requests return a uniform response to prevent account enumeration. The response reports the request outcome; it does not confirm that an email was sent or delivered. An already registered email address will not receive another registration code. Sign in or reset your password instead.
Sign-In Methods
Enter your registered email and password, complete the bot verification, and submit.
- Consecutive failed attempts will trigger rate limiting; wait before retrying.
- Standalone TOTP authenticator apps and 2FA are not currently enabled.
Session State & Multi-Device Security
- Page Redirects: Visiting the sign-in page while already signed in redirects back to your previous page. When an existing session expires, the page stays on the sign-in form without bouncing. If your session has expired or been revoked but the browser still holds its Cookie, opening a page that needs sign-in, such as
/dashboard,/profile,/subscriptions,/adminor fansub group management, takes you to the sign-in page and back to that page after you sign in. - Cross-Device Sign-Out: When signing out on another device, this device may still appear signed in for up to ~5 minutes due to local credential caching. However, sensitive operations (password changes, fansub management, publishing) immediately verify active server sessions.
