FAQs | Registrars
Frequently Asked Questions specific to our Registrar partners
GENERAL FAQs
If we are already accredited with Neustar (offering .biz or .us), do we need to pass another OT&E certification specifically for .tel?
Yes, there are minor differences in EPP syntax used with .tel. Therefore a separate OT&E testing session with Neustar will be required. You can find more details about EPP differences in the EPP QuickStart Guide.
Multiple registrars within the same group of companies that share their registration infrastructure may not need to test multiple times, please check before you proceed.
Can registrants use .tel for an email address (i.e. [email protected])?
Yes. If an end-user wishes to activate email addresses for a .tel domain then the following additional components to our service will be required:
- a mail server set up by the registrar or a third party provider (with a hostname not in .tel)
- an MX record within the .tel domain that points to that mail server hostname. This MX record can be inserted into a .tel zone by means of a SOAP API command, or in the web control panel settings.
Can registrars upsell their own privacy services on top of .tel domains?
We don’t make any demands of registrars regarding their privacy services and .tel domains. However, there are some guidelines we recommend are followed. In so far as we ask registrars that offer privacy services to ensure that such services comply with the .tel systems, i.e. TelFriends. For TelFriends to function correctly, an email sent to the registrant’s e-mail address (as listed in the SRS) has to be deliverable to the actual registrant.
This is required in order to correctly associate TelFriends accounts and .tel domains. If you are publishing a privacy service email contact then please ensure your systems pass on any Telfriending requests to the actual registrants nominated email contact.
How are SRS connections allotted?
Production SRS: up to 15 connections per registrar spread across no more than two /27 subnets. OT&E SRS: up to 7 connections per registrar spread across no more than two /27 subnets.