Account, account classes & limits
A free IPv64.net account is enough for DynDNS, health checks, DNS failover and much more. This page explains how to create your account, how the account classes Free, Home / Supporter, Business and Company differ, where to find your update token and API key, and how to secure or delete your account.
Create an account
- Register
Open ipv64.net/account, enter your e-mail address under “Register new account” and accept the terms and conditions. You can optionally subscribe to the newsletter about new features and incidents. - Check your e-mail
You receive an e-mail with a generated password and a link that activates the account. The update URL and the API only work after activation. - Log in and change your password
Log in with e-mail and password and set your own password in the account settings (at least 8 characters). - Create your first domain
Continue with DynDNS domains.
Forgot your password? Enter your e-mail address under “Forgotten password” on the same page; IPv64.net sends you a new password.
Registration is protected by reCAPTCHA. If it fails, a different browser often helps, or typing the e-mail address by hand instead of using autofill.
Account classes and prices
The Free account stays free. With a higher account class you support the project and get higher limits.
| Account class | Price per year | Use | E-mail support |
|---|---|---|---|
| Free | €0 | personal | no (forum) |
| Home / Supporter | €40 | personal | yes |
| Business | €100 | business | yes |
| Company | €200 | business | yes |
- All prices include statutory VAT.
- One-off payment for 365 days, no subscription: there is no automatic renewal and no follow-up cost. You renew yourself.
- Renewing: If you book again before expiry, one year is added to the remaining time.
- Payment: via PayPal under Account > account class or via the buttons on ipv64.net/pricing. The billing address is the one stored at PayPal; the invoice arrives digitally a few hours after booking. For bank transfer or other payment methods, write to info@ipv64.net.
- Partner programme: credit from the partner programme is deducted on purchase.
How long your account class is still valid is shown in the overview after logging in at ipv64.net/account.
Limits compared
The limits are stored in the IPv64.net database and may change. The values below match the pricing page (as of October 2026); ipv64.net/pricing is always authoritative. Your own limits are also returned by the API (get_account_info).
DynDNS and API
| Free | Home / Supporter | Business | Company | |
|---|---|---|---|---|
| DynDNS domains | 3 | 10 | 50 | 256 |
| Own domains (DNS only) | 0 | 3 | 10 | 50 |
| DynDNS TTL | 60 s | 10 s | 10 s | 10 s |
| DynDNS updates per day | 64 | 1024 | unlimited | unlimited |
| API calls per day | 512 | unlimited | unlimited | unlimited |
Health checks and DNS failover
| Free | Home / Supporter | Business | Company | |
|---|---|---|---|---|
| Health checks | 3 | 10 | 50 | 250 |
| Health check checks per day | 1024 | 8192 | unlimited | unlimited |
| Shortest health check interval | 2 min | 30 s | 30 s | 30 s |
| Health check logs | 500 | 1000 | 5000 | 10000 |
| DNS failover policies | 1 | 5 | 25 | 50 |
| DNS failover monitors | 2 | 25 | 100 | 250 |
| DNS failover rules | 2 | 50 | 100 | 250 |
| Offline pages | 1 | 5 | 25 | 50 |
| Notifications | unlimited | unlimited | unlimited | unlimited |
| SMS per day (Germany only) | 5 | 50 | unlimited | unlimited |
Cloud Router and VPN
| Free | Home / Supporter | Business | Company | |
|---|---|---|---|---|
| Internet access | limited | 50 Mbit/s | 1 Gbit/s | 1 Gbit/s |
| Cloud Routers | 1 | 3 | 10 | 25 |
| VPN gateways | 1 | 3 | 10 | 32 |
| VPN peers / clients | 2 | 6 | 20 | 64 |
| Gateway speed (+burst) | 8 Mbit/s | 50 Mbit/s | 1 Gbit/s | 1 Gbit/s |
| Gateway traffic per month (in + out) | 50 GB | 1 TB | 10 TB + | 10 TB ++ |
| Own public IPv4 / IPv6 | IPv4 paid, IPv6 included | IPv4 paid, IPv6 included | IPv4 paid, IPv6 included | IPv4 paid, IPv6 included |
| Hardware gateways | no | no | yes | yes |
CDN64 and DNS server
| Free | Home / Supporter | Business | Company | |
|---|---|---|---|---|
| CDN domains (names in CDN64) | 1 | 5 | 10 | 25 |
| Port mappings (CDN64 port mapper) | 2 | 10 | 50 | 250 |
| CDN64 cache per name (mode 3) | 16 MB | 256 MB | 1024 MB | 4096 MB |
| CDN bandwidth (all edge servers together) | 50 Mbit/s | 1 Gbit/s | unlimited | unlimited |
| CDN64 tunnel connections per server | 1 | 1 | 2 parallel | 4 parallel |
| CDN traffic per month (in + out) | 10 GB | 100 GB | 10 TB | 20 TB |
| Dynamic DNS clients (DNS64) | 1 | 5 | 10 | 50 |
| DNS queries | unlimited | unlimited | unlimited | unlimited |
| Blocklists | ads + tracking | all | all | all |
What the CDN values mean and what happens when the traffic is used up is explained under CDN64 → quota and traffic.
Daily limits and reset
IPv64.net resets the daily counters for DynDNS updates, API calls, health check checks and SMS to 0 once a day. Traffic limits for CDN64 and Cloud Router apply per month. When a daily limit is reached, the updater and the API reject further requests with 429 until the reset (see update URL and API). When the health check limit is reached, you receive an e-mail.
Update token and API key
Your account has two kinds of keys – for DynDNS updates and for the API. Both are 32 characters long. Treat them like passwords.
| Key | Used for | Where |
|---|---|---|
| Account Update Token | DynDNS update of all domains | in the account box on the account pages and as “Account Update URL” in every domain |
| Domain key (domain update token) | DynDNS update of one domain | domain settings on ipv64.net/dyndns |
| Record token | DynDNS update of one record | at the individual record |
| Account API key | API v1 and v2 | in the account box on the account pages |
| API keys | API v1 and v2 | Account > API |
You regenerate the Account Update Token, the domain key and the account API key with the arrow icon next to the key; the old key stops working. How the update keys are used is explained under Update URL & protocol.
Managing API keys
Under Account > API you create as many API keys as you like – ideally one per device or script:
- Name of your choice (default “New API-Key”),
- Expiry: 1 hour, 6 hours, 1 day, 1 week, 1 month, 1 year or never,
- “Used” column: how often the key has been used,
- QR code to transfer the key to the app,
- trash icon to delete immediately.
New accounts automatically get a key named “Default” without an expiry date. What you can do with the API is described under API.
Account security and two-factor login
In the account settings (Account Settings) you can
- change your password (at least 8 characters),
- change your e-mail address (the new address must not be registered yet),
- choose a user name (4 to 63 characters, unique),
- manage two-factor authentication (2FA).
Two-factor authentication (2FA)
With 2FA, IPv64.net asks for a one-time code in addition to your password. Two methods are available:
- Google OTP (TOTP): with Google Authenticator or another TOTP app. Scan the QR code, enter your current password and the first code. There is one TOTP key per account.
- YubiKey OTP: add a YubiKey with a name and touch it once. You can register several YubiKeys.
The overview under Account > 2FA lists all keys with creation and last-use date; you also remove them there.
Sharing your account
Under “Share my Account” you give another IPv64.net account access to yours, e.g. your IT service provider. Once they accept, they can log into your account without password and without 2FA. The list shows status and last use; both sides can remove the share at any time. Via API v2 the other person can work in your account with their own key (header X-IPv64-Act-As).
Logins, failed logins, newly generated update tokens and created or deleted API keys are listed in the account log at ipv64.net/logs.
View your data and delete your account
Under “Data privacy” in the account settings, “Show all my Data” shows the account data stored for you.
“Delete my Account - NOW” deletes your account. To confirm, enter your current password.
All data of the account is deleted immediately and irrevocably: domains with all records, health checks with events, DNS failover policies, offline pages, status pages, integrations, API keys, 2FA keys, shares and logs, plus your CDN64 names with tunnels, certificates, access lists and port mappings – the edge servers drop them the next time they fetch their configuration. Cloud Router gateways and DNS64 clients are removed from the servers in the background. Recovery is not possible.
Found a mistake or missing something? Tell us in the v64.tech forum. · Updated: 2026-11-02