CINXE.COM

<!DOCTYPE html>  <html> <head> <meta charset=UTF-8> <title>ZISPA - Home page</title> <script src="./js//jquery.min.js"></script> <link rel='stylesheet prefetch' href='./css/font-awesome.min.css'> <link rel=stylesheet href="css/normalize.css"> <link rel=stylesheet href="css/bootstrap.css"> <link rel=stylesheet href="css/style.css"> <script src="./fancybox/lib/jquery-1.10.1.min.js"></script> <script src="./fancybox/lib/jquery.mousewheel-3.0.6.pack.js"></script> <script src="./fancybox/source/jquery.fancybox.js?v=2.1.5"></script> <link rel=stylesheet type="text/css" href="./fancybox/source/jquery.fancybox.css?v=2.1.5" media=screen /> <link rel=stylesheet type="text/css" href="./fancybox/source/helpers/jquery.fancybox-buttons.css?v=1.0.5"/> <script src="./fancybox/source/helpers/jquery.fancybox-buttons.js?v=1.0.5"></script> <link rel=stylesheet type="text/css" href="./fancybox/source/helpers/jquery.fancybox-thumbs.css?v=1.0.7"/> <script src="./fancybox/source/helpers/jquery.fancybox-thumbs.js?v=1.0.7"></script> <script src="./fancybox/source/helpers/jquery.fancybox-media.js?v=1.0.6"></script> <script>$(document).ready(function(){$('.fancybox').fancybox();$(".fancybox-effects-a").fancybox({helpers:{title:{type:'outside'},overlay:{speedOut:0}}});$(".fancybox-effects-b").fancybox({openEffect:'none',closeEffect:'none',helpers:{title:{type:'over'}}});$(".fancybox-effects-c").fancybox({wrapCSS:'fancybox-custom',closeClick:true,openEffect:'none',helpers:{title:{type:'inside'},overlay:{css:{'background':'rgba(238,238,238,0.85)'}}}});$(".fancybox-effects-d").fancybox({padding:0,openEffect:'elastic',openSpeed:150,closeEffect:'elastic',closeSpeed:150,closeClick:true,helpers:{overlay:null}});$('.fancybox-buttons').fancybox({openEffect:'none',closeEffect:'none',prevEffect:'none',nextEffect:'none',closeBtn:false,helpers:{title:{type:'inside'},buttons:{}},afterLoad:function(){this.title='Image '+(this.index+1)+' of '+this.group.length+(this.title?' - '+this.title:'');}});$('.fancybox-thumbs').fancybox({prevEffect:'none',nextEffect:'none',closeBtn:false,arrows:false,nextClick:true,helpers:{thumbs:{width:50,height:50}}});$('.fancybox-media').attr('rel','media-gallery').fancybox({openEffect:'none',closeEffect:'none',prevEffect:'none',nextEffect:'none',arrows:false,helpers:{media:{},buttons:{}}});$("#fancybox-manual-a").click(function(){$.fancybox.open('1_b.jpg');});$("#fancybox-manual-b").click(function(){$.fancybox.open({href:'iframe.html',type:'iframe',padding:5});});$("#fancybox-manual-c").click(function(){$.fancybox.open([{href:'1_b.jpg',title:'My title'},{href:'2_b.jpg',title:'2nd title'},{href:'3_b.jpg'}],{helpers:{thumbs:{width:75,height:50}}});});});</script> <script>$(document).ready(function() { $('input').bind('keypress', function(event) { var regex = new RegExp("^[-a-zA-Z0-9\b]+$"); var key = String.fromCharCode(!event.charCode ? event.which : event.charCode); if (!regex.test(key)) { event.preventDefault(); return false; } }); $('input').keyup(function() { var empty = false; $('input').each(function() { if ($(this).val().length == 0) { empty = true; } }); if (empty) { $('.actions input').attr('disabled', 'disabled'); } else { $('.actions input').attr('disabled', false); } }); $("#btnSearch").click(function(event) { var term = $("#urlField").val(); perlExecute(term); }); function perlExecute(term) { $.ajax({ type: 'POST', url: '/cgi-bin/domain_lookup.pl', data: { 's': term }, success: function(res) { $("#result").html(res); }, error: function() { $("#result").html("Search Failed Possible reasons:-<br/><br/>There are illegal characters in your search, (Allowable characters are: a-z A-Z 0-9 and '-' within the domain name.)") } }); };});</script> <style>.fancybox-custom .fancybox-skin{box-shadow:0 0 50px #222;} body{max-width:700px;margin:0 auto;}</style> <style> .twoColumns { -webkit-column-gap: 10px; -moz-column-gap: 10px; column-gap: 10px; -webkit-column-count: 2; -moz-column-count: 2; column-count: 2; } .threeColumns { -webkit-column-gap: 10px; -moz-column-gap: 10px; column-gap: 10px; -webkit-column-count: 3; -moz-column-count: 3; column-count: 3; text-align: center; } .tg {border-collapse:collapse;border-spacing:0;} .tg td{font-family:Arial, padding:5px 5px;border-width:1px;overflow:hidden;word-break:normal;} .tg th{font-family:Arial, padding:5px 5px;border-width:1px;overflow:hidden;word-break:normal;} .tg.center { margin-left:auto; margin-right:auto;} </style> <body> <p align=center><br> <span class=blue>Z</span><span class=white>imbabwe </span><span class=blue>I</span><span class=white>nternet </span><span class=blue>S</span><span class=white>ervice </span><span class=blue>P</span><span class=white>roviders </span><span class=blue>A</span><span class=white>ssociation</span></p> <div id=wrapper> <div id=left-side> <ul style="padding-right: 30px; padding-left: 20px;"> <li class="choose"> <font color=#0000ff size=5>Home</font> </li> <li class=pay active> <font color=#0000ff size=5>Domains</font> </li> <li class=wrap> <font color=#0000ff size=5>Members</font> </li> <li class=ship> <font color=#0000ff size=5>ZINX</font> </li> <li> <font color=#0000ff size=5><a class=fancybox href="#inline20" title="AGM">AGM</a></font> </li> </ul> </div> <div id=border> <div id=line class=one></div> </div> <div id=right-side> <div id=first> <h1>ZISPA</h1> <div class=col-md-12> <p align=justify>ZISPA (the Zimbabwe Internet Service Providers' Association) is an independent and voluntary association established to represent all the major ISPs in Zimbabwe and deal with matters relating to the provision of Internet access in Zimbabwe. ZISPA's mission is to provide a non-profit forum in which Internet Service Providers can address issues of common interest and interact with industry stakeholders so that end-users receive world-class service and industry participants earn a fair return on their investments.</br></br>ZISPA's main activities are:</p> <ul style="list-style-type:none"> <ul> <li type=disc> Management of the CO.ZW domain registry on behalf of the Zimbabwe Internet community</li> <li type=disc> Operation of the Zimbabwe Internet Exchange (ZINX)</li> </ul></ul> <p align=justify>CO.ZW domain names may be registered through any ZISPA member, including all major local ISPs as well as many web-related organisations. Non-Zimbabwean organisations may register by applying direct to ZISPA.</p> </div></div> <div id=second class=active> <h1> <br></h1> <div class=col-md-5> <div class="form input-group"> <input name=s type="text" class=form-control placeholder="domain" aria-describedby=basic-addon2 id=urlField> <span class="input-group-addon" id="basic-addon2">.co.zw</span> </div> </div> <div class=row></br> <div class=actions> <br><p align=center><input type=button value="Search for domain availability" id=btnSearch disabled></p> </div></div><div id=result></div> <table margin-left:15%; margin-right:15%; class="tg" width="70%"> <col width="60%"> <col width="40%"> <tr> <td class="tg-yw4l"> <p align=left><a class=fancybox href="#inline12" title="IMPORTANT NOTICE"><B>IMPORTANT NOTICE</B></a></p> <p align=left><a class=fancybox href="#inline2" title="What is a domain name?">What is a domain name?</a></p> <p align=left><a class=fancybox href="#inline10" title="Benefits of registering a domain name">Benefits of registering a domain name</a></p> <p align=left><a class=fancybox href="#inline11" title="Choosing a domain name">Choosing a domain name</a></p> <p align=left><a class=fancybox href="#inline5" title="Domain name registration procedure">Domain name registration procedure</a></p> <p align=left><a class=fancybox href="#inline9" title="Submission requirements (for registrars)">Submission requirements (for registrars)</a></p> </td> <td class="tg-yw4l"> <p align=left><a class=fancybox href="#inline6" title="Processing of applications">Processing of applications</a></p> <p align=left><a class=fancybox href="#inline3" title="ZISPA registration policies">ZISPA registration policies</a></p> <p align=left><a class=fancybox href="#inline4" title="Registration fees">Registration fees</a></p> <p align=left><a class=fancybox href="#inline7" title="Domain name disputes">Domain name disputes</a></p> <p align=left><a class=fancybox href="#inline8" title="Whois service">Whois service</a></p> </td> </tr> </table> <div id=inline2 style="width:700px;display: none;"> <h2>What is a domain name?</h2> <p align=justify>An Internet domain name is a unique identifier used to locate groups of associated computers and other network devices on the Internet. The domain name can be used to locate computer servers providing associated services for the domain, such as a website or email service.</p> <p align=justify>There are two general categories of domain name – those falling under a generic top level domain such as .com, .org, .net etc, and those under a country code top-level domain (ccTLD), eg .zw (Zimbabwe), .za (South Africa), .au (Australia) etc. In the case of ccTLD’s, there is normally a second-level domain (SLD) to describe the type of organisation registering the domain. Common SLD’s are:</p> <ul style="list-style-type:none"> <li type=none><b>ac</b>   Academic institutions</li> <li type=none><b>co</b>   Commercial organisations</li> <li type=none><b>gov</b> Government organisations</li> <li type=none><b>net</b>  Network-related organisations (not used in Zimbabwe)</li> <li type=none><b>org</b> Other organisations (typically non-profit)</li> </ul> <p align=justify>At the third level is the specific part of the domain name. The above three levels are combined to form the fully qualified domain name (FQDN) as follows:</br> <ul style="list-style-type:none"><li>name.SLD.ccTLD (eg zispa.org.zw)</li></ul> ZISPA manages the registry responsible for the CO.ZW namespace, so we register domain names of the form: example.co.zw. By registering a domain name, we identify the servers that hold the information relating to that domain. These are called “domain name servers” or just “nameservers”. It is important to note that ZISPA does not host the detailed DNS (Domain Name System) records for the domain (eg the information regarding the names of your email and web servers). Those records are held by the domain registrar or other DNS hosting company that maintains the nameservers to which the domain is delegated by the ZISPA nameserver.</p> </div> <div id=inline3 style="width:700px;display: none;"> <h2>ZISPA registration policies</h2> <p align=justify> POTRAZ regulations require that domain registrants provide accurate owner details. In support of these regulations, ZISPA requires that registrants provide their registrar with a copy of their national ID in the case of individuals or the certificate of incorporation in the case of a company. The details of the real owner must be provided in the application template, even if the domain registration procedure is being carried out by a consultant on their behalf. ZISPA strongly objects to consultants etc who register their clients' domains under their own name, as this is not only a violation of POTRAZ regulations, but may also lead to problems when there is a dispute between the real owner and their consultant. <br><br> The CO.ZW registry is not an open registry such as .COM where it is simply a matter of first come, first served. We vet all applications in accordance with the following policies:</p> <ul> <li type=disc>Known company/organisation names will not be registered without authority from the body concerned. For example, we would not register yahoo.co.zw without authorisation from Yahoo. In case of doubt we may request proof of company registration. <li type=disc>Names of schools, clubs, churches etc must be registered in the name of those organisations, not of individuals. <li type=disc>Zimbabwean place names are reserved for the use of the corresponding national or local government authority. <li type=disc>We strongly object to cyber-squatting and will do what we can to prevent attempts at registering domains for that purpose. </ul> <p align=justify>In addition to the above, all applications must comply with our standard <a target="_blank" href="http://zispa.org.zw/terms_and_conditions.html">ZISPA Terms and Conditions</a>. Of particular importance are the following:</p> <ul> <li type=disc> The applicant must have a bona fide intention to use the domain name on a regular basis on the Internet.</li> <li type=disc> The use or registration of the domain name by Applicant does not or will not interfere with, nor infringe the right of any third party in any jurisdiction with respect to trademark, service mark, tradename, company name, close corporation name, copyright or any other intellectual property right.</li> <li type=disc> At the time of submission, the registrar and/or registrant must already have configured at least two operational nameservers to which the domain can be delegated.</li> <li type=disc> The nameservers must continue to be fully connected to the Internet and be able to respond authoritatively to queries on the domain.</li> </ul> </div> <div id=inline4 style="width:700px;display: none;"> <h2>Registration fees</h2> <p align=justify>Registration fees are a matter to be decided between the registrant (ie the applicant for the domain name) and their chosen registrar.</br></br> ZISPA will charge registrars separately for registrations and registration renewals. Non-ZISPA member registrars are charged USD35 per domain and USD35 per annum renewal fee. There is no charge for modifications.</p> </div> <div id=inline5 style="width:700px;display: none;"> <h2>Domain name registration procedure</h2> <p align=justify>The person or company that wishes to register a domain name is known as the registrant. The registrant should deal with a registrar, not with ZISPA directly. Zimbabwe residents are advised to use a ZISPA registrar, which includes most local Internet Service Providers as well as major local website developers. For a full list, see our <b>Members</b> section. Non-residents may choose to contact a ZISPA registrar or a foreign registrar of their choice.</br></br> <strong>New registrations</strong></br></br> The registrant must provide the following documents (normally as a scanned image) to their registrar: <ul> <li type=disc> A letter on the registrant's letterhead (in the case of a company or organisation) or a letter with a certified copy of their identification details in the case of an individual. This should specify the name of the domain to be registered and the name of the registrar nominated to register the domain on their behalf, eg a letter saying "Please register the following domain for our company/myself" is all that is needed. Corporate applications must be signed by a suitably authorised person from the applicant company, and the name and position of the person must be spelt out.</li> <br> <li type=disc> The letter must confirm acceptance of <a href="http://zispa.org.zw/terms_and_conditions.html">ZISPA Terms and Conditions</a> which may be varied from time to time and listed on our website.</li> </ul> The registrar is required to keep the above copies securely, to be made available to <a target="_blank" href="http://www.potraz.gov.zw/">POTRAZ</a> (the Postal and Telecommunications Authority of Zimbabwe) on demand.</br></br>The registrar must then email a completed <a target="_blank" href="http://zispa.org.zw/ZISPA_template">co.zw template</a>, containing the technical and contact details of the domain to be registered, as an ASCII attachment (saved in ANSI format) to admin(at)zispa.org.zw.</br></br> <strong>Modifications</strong></br></br> The registrant should contact the original registrar to arrange any modifications. It is the responsibility of that registrar to ensure that the request genuinely comes from the registrant. The registrar should then submit a <a target="_blank" href="http://zispa.org.zw/ZISPA_template">co.zw template</a> to ZISPA, again as an ASCII email attachment, with the updated details.</br></br> <strong>Transfer to new registrar</strong></br></br> The registrant should contact the new registrar to arrange for a transfer from their original registrar. They should also ask the original registrar to contact the new registrar authorising the release of the domain. It is the responsibility of the new registrar to ensure that the request genuinely comes from the registrant and that the domain has been released by the original registrar.</br></br> The new registrar should then submit a <a target="_blank" href="http://zispa.org.zw/ZISPA_template">co.zw template</a> to ZISPA together with (a) an email from the registrant confirming the transfer, and (b) an email from the original registrar confirming the release of the domain to the new registrar. The three attachments should be sent with the one email.</br> </br> For registrar transfers, the action specified in Item 1b of the template should be T for Transfer.</br> </br> <strong>Transfer to new owner</strong></br></br> The new registrant should contact the current registrar to arrange for a transfer from the original registrant. They must provide a scanned, signed application letter confirming agreement to accept <a href="http://zispa.org.zw/terms_and_conditions.html">ZISPA Terms and Conditions</a> as in the case of a new registration. They should also provide proof of release from the original registrant.</br> </br> It is the responsibility of the registrar to ensure that the request genuinely comes from the new registrant and that the domain has been released by the original registrant.</br> </br> The registrar should then submit a <a target="_blank" href="http://zispa.org.zw/ZISPA_template">co.zw template</a> to ZISPA, again as an ASCII email attachment, together with an email from the original registrant confirming the transfer. The two attachments should be sent with the one email.</br> </br> For owner transfers using the same registrar, the action specified in Item 1b of the template should be M for Modify.</br> </br> If the new owner is using a different registrar, then an email release from the original registrar should also be attached.</br> </br> <strong>Domain name deletions</strong></br></br> To delete a single domain, the existing registrar should email a template to ZISPA with the action in Item 1b of the template being "D" for "Delete".</br> </br> Bulk deletions can be arranged by the registrar contacting ZISPA with a list of the domains that they manage and wish to have deleted.</br> </br> <strong>Bulk updates of nameservers</strong></br></br> Registrars who wish to make a bulk update of one set of nameservers to another for a group of their domains should contact ZISPA. We can arrange this without requiring the registrar to provide templates for each of these domains.</br></br> <strong>Nameserver glue records</strong></br></br> If the hostnames of the nameservers for a particular domain use that same domain they will be impossible to find without additional information. For example, if the domain example.co.zw uses the nameservers ns1.example.co.zw and ns2.example.co.zw then the domain example.co.zw cannot be found without knowing the IP addresses of these nameservers. These nameserver IP addresses must be registered separately with corresponding glue records at ZISPA. This requirement should be specified in the email accompanying the application.</br> </br> If the IP addresses change at any stage it is the responsibility of the registrar to notify ZISPA so the glue records can be updated accordingly.</br> </br> Note that it is essential for such nameservers to have their own A records configured, ie ns1.example.co.zw must be registered on itself as well as having its glue record at ZISPA.</br> </br> </p> </div> <div id=inline6 style="width:700px;display: none;"> <h2>Processing of applications</h2> <p align=justify>ZISPA aims to process all applications within one working day. During working hours, applications are normally processed within an hour or so. Applications received outside normal working hours, including weekends and public holidays, are normally processed at least once per day, but often within a matter of hours up until late evening.<br><br> ZISPA carries out a range of verification checks on the templates before processing them. These include checking that:</p> <ul> <li type=disc> The action requested is appropriate and consistent with the registrar and current domain owner if applicable.</li> <li type=disc> The application conforms to ZISPA registration policies.</li> <li type=disc> All required fields have been completed accurately.</li> <li type=disc> The listed domain owner is the real owner and not a consultant etc acting on behalf of a client.</li> <li type=disc> The domain name is a fully qualified, third level co.zw domain name, eg example.co.zw, and not a subdomain such as mail.example.co.zw, www.example.co.zw or a non-co.zw domain name.</li> <li type=disc> All nameservers actually exist.</li> <li type=disc> The IP addresses listed for the nameservers are correct. (Where a nameserver has more than one IP address, only one should be listed.)</li> <li type=disc> There are between two and four unique nameservers (ie having different IP addresses, not just different hostnames).</li> <li type=disc> All nameservers have unique A records (not CNAME records).</li> <li type=disc> All nameservers are authoritative at the time of submission, ie:</li> <ul> <li type=disc> They respond to queries on the domain.</li> <li type=disc> Their response has an aa (authoritative) header flag.</li> <li type=disc> They list at least NS and SOA records for the domain.</li> </ul> <li type=disc> The NS records on the registrar's nameservers match the list of nameservers registered with ZISPA for the domain. (Vanity nameserver hostnames listed at ZISPA will however be accepted as long as their IP addresses match those of the actual nameservers listed in the NS records on the vanity nameservers.)</li> <li type=disc> All nameservers have the same serial number in the SOA record.</li> </ul> <p align=justify>Where there is a change of owner or registrar, we check for the required release letters from the original owner/registrar. Once passed, the domain and its nameservers are then registered on the ZISPA nameserver (ns1.zispa.org.zw) and its associated secondary nameservers located in various parts of the world.</br></br>The registrar will then receive a manual reply to their email. This will then be followed by an automated confirmation message sent to all parties concerned, reporting the nameservers that have been registered for the domain, as well as the results of a test of those nameservers to check that they are authoritative and consistent. </br></br>Registrants are advised to contact their registrar, and not ZISPA, in case of any errors noted in the confirmation emails. ZISPA reserves the right to cancel the registration if any of the confirmation emails to the addresses listed in the template bounce back due to an invalid address or misconfigured mail server.</p> </div> <div id=inline7 style="width:700px;display: none;"> <h2>Domain name disputes</h2> <p align=justify>Under no circumstances whatsoever shall ZISPA be obliged to act as an arbiter of disputes arising out of the registration and use of a domain name. Should ZISPA be presented with evidence that indicates that a domain name violates the rights of a third party, ZISPA shall be entitled to provide the complainant with the applicant's name and address and all further communication should exclude ZISPA. ZISPA will have no further obligations to the Applicant or complainant.</br></br> From our Terms and Conditions:</br></br> ZISPA WILL UNDER NO CIRCUMSTANCES WHATSOEVER AND HOWSOEVER ARISING BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING, WITHOUT LIMITATION, LOSS OF USE, BUSINESS INTERRUPTION OR LOST PROFITS), REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT, DELICT, OR OTHERWISE, EVEN IF ZISPA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. WITHOUT DEROGATING FROM THE AFOREGOING, ZISPA's LIABILITY FOR DIRECT DAMAGES ARISING OUT OF THIS AGREEMENT SHALL UNDER NO CIRCUMSTANCES EXCEED THE REGISTRATION OR AMENDMENT FEE, AS THE CASE MAY BE, PAYABLE BY APPLICANT.</p> </div> <div id=inline8 style="width:700px;display: none;"> <h2>Whois service (who is the owner of a domain?)</h2> <p align=justify>ZISPA does not provide an online whois service at present. However requests for this information on individual domains can be sent to admin(at)zispa.org.zw.</p> </div> <div id=inline9 style="width:700px;display: none;"> <h2>Submission requirements (for registrars)</h2> <p align=justify><strong>Before applying to ZISPA:</strong></p> <ul> <li>For new registrations, make sure that the domain name is available to be registered. You may use the Search facility behind this popup. <li>For new registrations, check that the domain name does not conflict with ZISPA's registration policies. <li>Create the required DNS records on the primary nameserver for the domain. At a minimum these should include the SOA and NS records, with the nameservers in the NS records matching those in the template to be submitted to ZISPA. Normally MX and A records would be added at this time. <li>Configure the secondary nameserver(s). Between one and three secondaries are required. They should slave off the primary nameserver. <li>Check to make sure that the nameservers are working correctly and do respond authoritatively to queries on the domain. <li>Check again that the nameservers specified in the NS records match the list of nameservers being registered with ZISPA and that they all have identical serial numbers. <li>Check that all email addresses listed in the template are valid and operational, especially if they are in the domain being registered. This means that SMTP routing should be operational and correctly configured for the domain. </ul> <strong>Email requirements:</strong></br> <p align=justify>The key input required by ZISPA is the email request from the registrar with the completed <a target="_blank" href="http://zispa.org.zw/ZISPA_template">co.zw template</a>. The email should:</p> <ul> <li> Be sent from the standard email address registered by the registrar with ZISPA.</li> <li> Be addressed to admin(at)zispa.org.zw.</li> <li> Have a subject line that indicates the action required and the fully qualified domain name, eg "Add example.co.zw" or "Transfer example.co.zw".</li> <li> Have only one template attached, which should be in ASCII format saved with ANSI encoding (<em>not</em> UTF encoding, which cannot be processed).</li> <li> Include any required associated emails (eg owner or registrar releases). Do not forward these separately.</li> </ul> Note that a separate email is required for each domain being processed. Do not include multiple templates in the same email as we need to send separate replies for each domain. <p align=justify><strong>The templates:</strong></p> <ul> <li> Must not be modified in format in any way apart from the addition of the required data.</li> <li> Data must be entered to the right of the corresponding colon on a single line without any word wrap.</li> <li> All fields marked with an asterisk on the template must be completed accurately.</li> <li> The registrar should use the handle that they have been previously allocated by ZISPA in Items 3a and 5a. Otherwise leave the fields blank.</li> </ul> <p align=justify>The key technical data required is in Section 6: The hostnames of the nameservers at Items 6a and 6c, and optionally at Items 6e and 6g. For verification purposes, we require their IP addresses to be specified in Items 6b, 6d, 6f and 6h. The registrar should ensure that there are at least two nameservers and that they are independent, authoritative and operational for the domain at the time of submission and at all times thereafter.</p> <p align=justify><strong>Common problems with applications:</strong></p> <ul> <li>Applications for new domain registrations when the domain is already registered. <li>Attempts to register fourth-level subdomains, including www type subdomains, such as mail.example.co.zw or www.example.co.zw. (ZISPA does not register subdomains beyond the third level. Fourth-level subdomains are the responsibility of the domain registrar.) <li>Specifying nameservers that are not already authoritative for the domain. <li>Invalid or redundant nameserver hostnames and IP addresses. (A minimum of two distinct nameservers are required.) <li>NS records for the domain that do not match the list of nameservers being registered with ZISPA. <li>Correspondence without the domain name in the subject line (making followups very difficult when trying to trace related correspondence). <li>Correspondence where the domain name in the subject line does not match the domain in the template. <li>Correspondence with multiple templates attached. <li>Use of outdated domain registration templates. <li>Templates sent as inline text rather than as attachments. <li>Templates saved in non-ASCII + ANSI format. <li>Templates that have been modified in some way other than by data entry to the right of the colon separator. <li>Missing fields (eg lack of addresses, phone numbers and email addresses in the templates, and especially item 4 - Description of organisation/domain). <li>Invalid fields, especially email addresses. (Note that registrations with invalid email addresses are liable to be cancelled without further notice.) <li>Missing physical address for Item 7 - Domicilium Citandi et Executandi. (This may seem an irritation, but from ZISPA's perspective, this is an essential requirement in case of any legal issue arising in the future.) </ul> </div> <div id=inline10 style="width:700px;display: none;"> <h2>Benefits of registering a domain name</h2> <p align=justify>For a company or organisation that wishes to brand itself to the public, a domain name is an essential identifier along with their company/organisation name, trademark and logo. It can be used for an associated website that can be easily located on the Internet, and also for email addresses that are immediately associated with that body rather than with a generic email service provider such as Gmail or Yahoo.</br> </br> The use of a domain for a company or organisation’s email addresses means that they can then take control over their emails by routing them through a mail server that can be customised to their specific requirements.</br> </br> On a technical level, having a domain name means that you can list DNS (Domain Name System) records for the domain which can be readily located on the Internet. These records can provide information such as:</br> <ul> <li>The hostnames of the servers to which mail for the domain should be delivered (MX records). <li>The IP address of the server hosting the domain's website (A record). <li>Text information of any kind (TXT records). <li>DNS records for any subdomains. <li>The hostnames of the nameservers for the domain (NS records). <li>The contact address of the person responsible for managing the domain (part of the SOA record). </ul> <br> </p> </div> <div id=inline11 style="width:700px;display: none;"> <h2>Choosing a domain name</h2> <p align=justify>For a domain name to be useful, it should be as simple and memorable as possible. Very long domain names will cause problems for people wanting to send emails or access the associated website. Try to use memorable initials rather than full names in the case of companies or organisations having long names. For example, if there was a company called “Cheap Zimbabwean Domain Names” they would probably be better off registering the name czdn.co.zw rather than say cheapzimbabweandomainnames.co.zw. However something like zimdom.co.zw would be easier to remember.</br></br>Note that long domain names also carry the risk of misinterpretation. Wikipedia gives examples of the registrants of “Who Represents” and “Therapist Finder” choosing the unfortunate domain names whorepresents.com and therapistfinder.com respectively. In such cases a hyphen could have been used to break up the words, eg who-represents.com.<br><br>Domain names may use only the following characters: a-z, A-Z, 0-9 and “-“ (as long as it is not the first character). Underscores in particular are not allowed. Note that capitalised letters in a domain name are functionally the same as lower-case letters, the only difference being in the way they are displayed.</br></br>You may check to see if a domain name is available by using the search box behind this popup.</p> </div> <div id=inline12 style="width:700px;display: none;"> <h2>IMPORTANT NOTICE</h2> <p align=justify>From the beginning of July 2016 ZISPA will implement more rigorous checks on templates before processing applications. This is intended to improve the standard of the Internet environment in Zimbabwe. Registrars will be required to ensure that:<br> <ul> <li>There are between two and four unique nameservers for the domain. <li>All nameservers have unique A records (not CNAME records). <li>The nameserver hostnames match the nameserver IP addresses in the template. <li>All nameservers are authoritative at the time of submission, ie:<br> - They respond to queries on the domain.<br> - Their response has an aa (authoritative) header flag.<br> - They list at least NS and SOA records for the domain. <li>The NS records on the registrar's nameservers match the list of nameservers registered with ZISPA for the domain. <li>All nameservers list same serial number in the domain's SOA record. <li>All email addresses listed in the template are valid and operational. </ul> Any applications that fail to meet all the requirements above will not be processed immediately, but will be reviewed every hour for 24 hours. If at the end of that time the requirements have not been satisfied the application will be rejected.<br> <br> Any applications that are found to have non-working email addresses after processing will be reversed. <br> </p> </div> </div> <div id=third> <table class="tg" width="98%"> <col width="2%"> <col width="35%"> <col width="4%"> <col width="60%"> <tr> <th class="tg-yw4l"> </th> <th class="tg-yw4l"><h2 align=left>Internet Service Providers</h2></th> <th class="tg-yw4l"><h2 align=center></h2></th> <th class="tg-yw4l"><h2 align=left>IT Consulting, Website Design and Hosting</h2></th> </tr> <tr> <td class="tg-yw4l"> </td> <td class="tg-yw4l"> <a href=http://www.africom.co.zw>Africom Zimbabwe</a><br> <a href=http://claybytes.net>Clay Bytes Solutions</a><br> <a href=http://www.econet.co.zw>Econet Wireless</a><br> <a href=http://fbnet.co.zw>FBNet</a><br> <a href=http://www.frampolafrica.com>Frampol</a><br> <a href=http://zimbabwe.liquidtelecom.com>Liquid Telecom</a><br> <a href=http://powertel.co.zw>Powertel</a><br> <a href=http://sadacnet.com>SADACNET</a><br> <a href=http://www.telco.co.zw/newtelco>Telco</a><br> <a href=http://www.telecel.co.zw>Telecel</a><br> <a href=http://www.utande.co.zw>Utande</a><br> <a href=http://zarnet.ac.zw>ZARNet</a><br> <a href=https://zodsat.com>ZODSAT</a><br> <a href=http://www.zol.co.zw>ZOL Zimbabwe</a> </td> <td class="tg-yw4l"> </td> <td class="tg-yw4l"> <div class="twoColumns"> <a href=http://advertguru.co.zw>Advert Guru</a><br> <a href=https://www.facebook.com/Afrohost-1468037303408442>Afrohost</a><br> <a href=https://www.akoiweb.co.zw>Akoiweb</a><br> <a href=http://www.angelwalt.co.zw>Angel&Walt</a><br> <a href=https://www.attelecoms.co.zw/home>AT Telecoms</a><br> <a href=https://atomistic.co.zw>Atomistic Solutions</a><br> <a href=https://castellumsystems.com>Castellum Integrated Systems</a><br> <a href=https://centricdata.net>Centric Data</a><br> <a href=https://cloudplusafrica.com>Cloud Plus Africa</a><br> <a href=http://www.crediblebrands.co.zw>Credible Brands</a><br> <a href=http://cyberplexafrica.com>Cyberplex Africa</a><br> <a href=http://designat7.com>Design@7</a><br> <a href=https://www.ecowebzim.com>Ecowebzim</a><br> <a href=http://www.doskey.co.zw>Doskey Technologies</a><br> <a href=https://ehost.co.zw>Ehost</a><br> <a href=http://freshspot.co.zw>Freshspot</a><br> <a href=https://gethost.co.zw>GetHost Web Hosting</a><br> <a href=http://hansole.org>Hansole Investments</a><br> <a href=http://him.co.zw>Hectic Interweb Magic</a><br> <a href=http://www.infocraft.co.zw>Infocraft</a><br> <a href=https://innovatehosting.co.zw>Innovate Hosting</a><br> <a href=https://www.index.co.zw>Internet Solutions Africa</a><br> <a href=http://www.jbkwebhosting.com>JBK Web Hosting</a><br> <a href=https://mango.zw/>Mango Email Service</a><br> <a href=http://marketingbyweber.com/incsub>Marketing By Weber</a><br> <a href=https://marmasco.com/>Marmasco Technologies</a><br> <a href=http://www.colinandcarl.co.zw>Minutus Promus Investments</a><br> <a href=http://myzimhost.co.zw>Myzimhost</a><br> <a href=http://neon.co.zw>Neolab Technology</a><br> <a href=https://www.nivacity.com/>NivaCity</a><br> <a href=https://pnrhost.com/>Pnrhost</a><br> <a href=http://rds.co.zw>Real Digital Systems</a><br> <a href=http://www.skylinepromo.com>Skylinepromo</a><br> <a href=http://starnet.co.zw>Starnet</a><br> <a href=http://statushitech.co.zw>Status Hi-Tech</a><br> <a href=http://tapali.co.zw>Tapali Technologies</a><br> <a href=https://terrifictech.africa>Terrific Tech</a><br> <a href="mailto:dnsadmin(at)thesourcedns.net">The Source</a><br> <a href=http://tremhost.com>Tremhost</a><br> <a href=https://www.uhostafrica.com>uHostAfrica</a><br> <a href=https://verticohost.com>Vertico Solutions</a><br> <a href=http://webenchanter.com>Web Enchanter</a><br> <a href=http://www.webdev.co.zw>Webdev</a><br> <a href=https://webzim.co.zw>Webzim</a><br> <a href=https://wehost.co.zw>Wehost</a><br> <a href="mailto:troy(at)zimbiz.net">Zimbiz Network</a><br> <a href=https://zhdconsulting.com/>ZHD Consulting</a><br> <a href=http://zimhero.com>Zimhero web solutions</a><br> <a href=http://zimhosts.com>Zimhosts</a><br> </div> </td> </tr> </table> </div> <div id=fourth> <h1>About ZINX</h1> <div class=col-md-12> <p align=justify>ZISPA operates ZINX, the Zimbabwe Internet Exchange, which provides for peering between local Internet Service Providers. This enables them to exchange traffic directly rather than routing it through third parties which may charge for the service. Peering between ZINX and other regional Internet exchanges is currently under consideration.</br></br>ZISPA members wishing to join ZINX should contact admin(at)zispa.org.zw for further details.</p> </div> </div> <div id=inline20 style="width:700px;display: none;"> <h2>ZISPA AGM 11 am Tuesday 18 May 2021</h2> <p align=justify>The following were elected to the new ZISPA Management Committee at the recent AGM:</p <div id=third> <h3>ISP Category (unopposed so no election was held)</h3> Kuda Chishumba (ZOL) <h3>Email Access Providers</h3> Reg Palterman (Mango) <br> Jacob Kudzayi Mutisi (Hansole) <h3>Auxiliary Members</h3> Rushmore Mushambi (Web Enchanter) </div> </div> </div> </div> <div id=wrappe> <div class=col-md-4> Copyright ZISPA 2016 </div> <div class=col-md-4> <p style="text-align: center;"> <a href="mailto:admin(at)zispa.org.zw">admin(at)zispa.org.zw</a></br> Tel: (+263) 08677-190909</br></p> </div> <div class=col-md-4> <p style="text-align: center;"> <a href="mailto:registry-accounts(at)mango.zw">registry-accounts(at)mango.zw</a></br> Tel: (+263) 0242-334111</br></p> </div> <div class=col-md-1> <!a href="#" class="social-button facebook"><!i class="fa fa-facebook"><!/i><!/a> </div> <div class=col-md-1> <!a href="#" class="social-button twitter"><!i class="fa fa-twitter"><!/i><!/a> </div> </div> <script src="./js/index.js"></script> <script> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-75163626-1', 'auto'); ga('send', 'pageview'); </script> </body> </html>