The purpose of this document is to describe the rules for the allocation of names within the c domain and its sub-domains.
2. PROCESS DETAIL
2.1 The rules given here apply to all requests for names in the .ts.io, .maid.build and .bitinflow.space domain and all sub-domains of .ts.io, .maid.build and .bitinflow.space except where differing rules exist for a sub-domain. The rules for a sub-domain shall incorporate all the rules in this document along with such additional rules that are required. Agreement of the Management of the Registry shall be required if the rules of a sub-domain are to exclude any of the rules of this document. Their agreement shall not unreasonably be withheld.
2.2 Where a dispute over the interpretation of the rules exists, the Management of the Registry shall rule on the interpretation.
2.3 All NEW domain requests will conform to RFCs 1034, 1035, 1122, 1123 and any subsequent replacements. For designated zones the requests may be handled by the automated Registration System. This Registration System will apply the appropriate RFCs, the rules and a check against the list of existing domain names. It may also check that operating nameservers exist for the request.
2.4 If the rules are changed in the future, some names approved under one set of rules might be rejected under the revised rules. No rule change will ever affect the status of a name which has been approved before the change unless sound technical reasons require this.
3. MANDATORY RULES FOR DOMAINS
3.1 An applicant may reside in any legal jurisdiction.
3.2 Certain single letter, two or more letters or number domain names are available for registration in a controlled and equitable manner.
3.3 There shall be at least two nameservers for the domain (with addresses specified in the request) operating at the time the request is submitted. There is no requirement for the nameserver to be physically located in any specific territory. There is no restriction on the IP address of these nameservers.
4. APPROPRIATE USE
No .ts.io, .maid.build and .bitinflow.space domain may be used, directly or indirectly, for any purpose that is sexual or pornographic or that is against the statutory laws of any Nation. In the event of the Registry being advised by any party that a specific site breaches this condition then the Registry reserves the right to immediately deactivate the offending registration.
5. UNSOLICITED COMMERCIAL E-MAIL (SPAM) MAIL POLICY
In the event that any .ts.io, .maid.build and .bitinflow.space domain is used either directly or indirectly for the purpose of directing unsolicited electronic mail (“spam mail”) either as the originator of the spam mail or as the address to which readers of spam mail are referred, then the Registry reserves the right to send a notice to the applicant to cease such spam mail. Should the applicant of the .ts.io, .maid.build and .bitinflow.space domain name fail to adhere to the conditions contained in such notice, then the Registry reserves the right to suspend or delete the operation of the offending .ts.io, .maid.build and .bitinflow.space domain name.
6. WHOIS DISCLOSURE OBLIGATIONS
Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database.
The WHOIS data is provided for informational purposes only. This service is intended only for query-based access. DE privacy laws limit the scope of information permitted for certain public access.
Therefore, concerns regarding abusive use of domain registrations should be directed to either (a) the Registrar of Record as indicated in the WHOIS output, or (b) the anti-abuse department at email@example.com.
7. CONTACT DATA ACCURACY
As per the Registry Terms and Conditions, all contacts associated with a domain name must supply accurate and verifiable contact information; specifically the full name of the legal entity or individual listed as the Domain Owner as well as the Administrative Contact and a physical street address for service of official notices along with a valid email address managed by each contact.