The OpenSRS system enforces character limits and supported character sets for each field in the Reseller Control Panel. Use this article to confirm the maximum length and allowed characters for any field before submitting data. Following these rules avoids validation errors during domain registration and account updates.
How field validation works
Character data types are strings that can include the upper and lower case alphabet, numbers, and symbols. Each field in the OpenSRS system has its own character limit and accepted character set. Required reseller information fields enforce additional formatting rules, such as phone number patterns and RFC 822 email validation.
Character limit for data fields
The table below lists the character limit for each data field in the OpenSRS system.
Field | Limit | Notes |
|---|---|---|
address1 | 64 | Conflicts in various areas |
address2 | 64 | Conflicts in various areas (optional) |
address3 | 64 | Conflicts in various areas (optional) |
city | 64 | |
country | 2 | |
domain | 80 | |
100 | ||
fax | 20 | Conflicts in various areas (optional) |
first_name | 64 | |
fqdn1 | 60 | Pattern: /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/ |
fqdn2 | 60 | Pattern: /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/ |
fqdn3 | 60 | Pattern: /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/ |
fqdn4 | 60 | Pattern: /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/ |
fqdn5 | 60 | Pattern: /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/ |
fqdn6 | 60 | Pattern: /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/ |
last_name | 64 | |
lang_pref | 2 | For .ca domains |
legal_type | 3 | For .ca domains |
org_name | 64 | |
postal_code | 32 | Required; "na" accepted as a placeholder |
phone | 20 | Conflicts in various areas |
period | 1-10 | Integer; 1 for renewal |
reg_username | 20 | |
reg_password | 20 | Must include 1 or more symbols (1S+) |
state | 32 | |
url | 255 | Optional |
Required reseller information data fields
The table below lists supported characters for each required field on the reseller information form.
Field | Supported characters |
|---|---|
Usernames | A-Z, a-z, 0-9 |
Passwords | A-Z, a-z, 0-9, and the symbols ! @ $ ^ , . ~ | = - + _ { } # " |
Phone numbers | Format: +CCC.NNNNNNNNNNNNxEEEE, where C is the country dial code, N is the number, and E is the extension. Use "x" only when an extension is specified. |
Fax numbers | Format: +CCC.NNNNNNNNNNNNxEEEE, where C is the country dial code, N is the number, and E is the extension. Use "x" only when an extension is specified. |
Email addresses | Validated against RFC 822 |
Note: Some address and phone fields are marked as having "conflicts in various areas." Test data carefully if you are submitting to multiple registries, since each registry may enforce stricter limits than the OpenSRS system overall.
Next steps
Validate input before submission. Check field length and character set against this reference before posting requests through the API or control panel.
Update stored data. Audit existing reseller and contact records to confirm they meet the current limits.
Review password rules. Confirm new passwords meet the symbol requirement. See Reset the Password of Your Reseller Control Panel.
Questions? Contact OpenSRS Support.
How helpful was this article?
Thanks for your feedback!
Do you still need help? If so please submit a request here.