| Prio | Original string | Translation | — |
|---|---|---|---|
| Example: "A @ {SERVER_IP} 300" creates an A record pointing the domain to your server with a 5-minute TTL. | Example: "A @ {SERVER_IP} 300" creates an A record pointing the domain to your server with a 5-minute TTL. | Details | |
|
Example: "A @ {SERVER_IP} 300" creates an A record pointing the domain to your server with a 5-minute TTL. Example: "A @ {SERVER_IP} 300" creates an A record pointing the domain to your server with a 5-minute TTL.
You have to log in to edit this translation.
|
|||
| Automatically create DNS records (like an A record pointing to your server) after domain registration. | Automatically create DNS records (like an A record pointing to your server) after domain registration. | Details | |
|
Automatically create DNS records (like an A record pointing to your server) after domain registration. Automatically create DNS records (like an A record pointing to your server) after domain registration.
You have to log in to edit this translation.
|
|||
| One nameserver per line. These will be set on the domain immediately after registration. | One nameserver per line. These will be set on the domain immediately after registration. | Details | |
|
One nameserver per line. These will be set on the domain immediately after registration. One nameserver per line. These will be set on the domain immediately after registration.
You have to log in to edit this translation.
|
|||
| Custom nameservers are required if you want domains to resolve to your WordPress multisite network. | Custom nameservers are required if you want domains to resolve to your WordPress multisite network. | Details | |
|
Custom nameservers are required if you want domains to resolve to your WordPress multisite network. Custom nameservers are required if you want domains to resolve to your WordPress multisite network.
You have to log in to edit this translation.
|
|||
| Choose whether to keep the registrar defaults or point to your own nameservers after registration. | Choose whether to keep the registrar defaults or point to your own nameservers after registration. | Details | |
|
Choose whether to keep the registrar defaults or point to your own nameservers after registration. Choose whether to keep the registrar defaults or point to your own nameservers after registration.
You have to log in to edit this translation.
|
|||
| Applied automatically after a domain is registered. Set custom nameservers to point domains to your hosting. | Applied automatically after a domain is registered. Set custom nameservers to point domains to your hosting. | Details | |
|
Applied automatically after a domain is registered. Set custom nameservers to point domains to your hosting. Applied automatically after a domain is registered. Set custom nameservers to point domains to your hosting.
You have to log in to edit this translation.
|
|||
| Default WHOIS contact details. Used as fallback when registrant info is not collected during checkout. | Default WHOIS contact details. Used as a fallback when registrant info is not collected during checkout. | Details | |
|
Default WHOIS contact details. Used as fallback when registrant info is not collected during checkout. Default WHOIS contact details. Used as a fallback when registrant info is not collected during checkout.
You have to log in to edit this translation.
|
|||
| If auto-renewal payment fails, how many days to keep retrying before giving up. | If auto-renewal payment fails, how many days to keep retrying before giving up. | Details | |
|
If auto-renewal payment fails, how many days to keep retrying before giving up. If auto-renewal payment fails, how many days to keep retrying before giving up.
You have to log in to edit this translation.
|
|||
| How many days before expiration to send the customer a renewal reminder email. | How many days before expiry to send the customer a renewal reminder email. | Details | |
|
How many days before expiration to send the customer a renewal reminder email. How many days before expiry to send the customer a renewal reminder email.
You have to log in to edit this translation.
|
|||
| When enabled, newly registered domains will have auto-renewal turned on by default. | When enabled, newly registered domains will have auto-renewal turned on by default. | Details | |
|
When enabled, newly registered domains will have auto-renewal turned on by default. When enabled, newly registered domains will have auto-renewal turned on by default.
You have to log in to edit this translation.
|
|||
| Controls how domains are renewed before expiration. Customers can override these on a per-domain basis from their account. | Controls how domains are renewed before expiration. Customers can override these on a per-domain basis from their account. | Details | |
|
Controls how domains are renewed before expiration. Customers can override these on a per-domain basis from their account. Controls how domains are renewed before expiration. Customers can override these on a per-domain basis from their account.
You have to log in to edit this translation.
|
|||
| Fetch the full list of available TLDs from your configured providers. This runs automatically once daily, or click to sync now. May take a few minutes. | Fetch the full list of available TLDs from your configured providers. This runs automatically once daily, or click to sync now. May take a few minutes. | Details | |
|
Fetch the full list of available TLDs from your configured providers. This runs automatically once daily, or click to sync now. May take a few minutes. Fetch the full list of available TLDs from your configured providers. This runs automatically once daily, or click to sync now. May take a few minutes.
You have to log in to edit this translation.
|
|||
| If a customer types "example.io", that TLD is checked first regardless of this list. These TLDs are used when the customer searches without specifying a TLD (e.g. just "example"). | If a customer types "example.io", that TLD is checked first regardless of this list. These TLDs are used when the customer searches without specifying a TLD (e.g. just "example"). | Details | |
|
If a customer types "example.io", that TLD is checked first regardless of this list. These TLDs are used when the customer searches without specifying a TLD (e.g. just "example"). If a customer types "example.io", that TLD is checked first regardless of this list. These TLDs are used when the customer searches without specifying a TLD (e.g. just "example").
You have to log in to edit this translation.
|
|||
| TLDs checked during domain search. The order determines result display order. Click "Sync Provider TLDs" below to load all available TLDs from your provider. | TLDs checked during domain search. The order determines result display order. Click "Sync Provider TLDs" below to load all available TLDs from your provider. | Details | |
|
TLDs checked during domain search. The order determines result display order. Click "Sync Provider TLDs" below to load all available TLDs from your provider. TLDs checked during domain search. The order determines result display order. Click "Sync Provider TLDs" below to load all available TLDs from your provider.
You have to log in to edit this translation.
|
|||
| Controls which TLDs are checked when a customer searches for a domain. This does not affect pricing — pricing is configured on each domain product. | Controls which TLDs are checked when a customer searches for a domain. This does not affect pricing — pricing is configured on each domain product. | Details | |
|
Controls which TLDs are checked when a customer searches for a domain. This does not affect pricing — pricing is configured on each domain product. Controls which TLDs are checked when a customer searches for a domain. This does not affect pricing — pricing is configured on each domain product.
You have to log in to edit this translation.
|
|||
Export as