gtld Registrar Manual Part V : Delta

Size: px
Start display at page:

Download "gtld Registrar Manual Part V : Delta"

Transcription

1 gtld Registrar Manual Part V : Delta Copyright Ó 2016 DNS Belgium vzw/asbl 1

2 Table of contents Table of contents Introduction Business rules Differences Commonalities EPP Differences Commonalities Registrar panel Differences DAS & WHOIS Differences Commonalities Registry actions with visibilty to the registrar/registrant Differences Commonalities Copyright Ó 2016 DNS Belgium vzw/asbl 2

3 1 Introduction This document is used to provide the registrars with the changes when migrating from the current system to DNS Belgium's new Registration system. 2 Business rules 2.1 Differences Following business rules are different before and after migration.. Action New Old Billing/Credits Domain renewal Grace periods Post-pay system, no credits. Both registry and registrar are protected from going into deep costs with the Protected transactions threshold. auto-renew per registrar is default and can't be turned off. The renew command is also implemented because of ICANN requirements. The EPP statusses ServerRenewProhibited / ClientRenewProhibited can be used by the registrar to disable the auto-renew feature on a per-domain basis. Auto-renews are prevented by this status. Renews are also prevented by this status (as per definition). DNS Belgium doesn t support grace periods as described in RFC Pre-pay system and virtual credits. Opt-in per registrar for auto-renew, default is set to active when a new registrar is created. Registrars can also send in renew commands. The EPP statusses ServerRenewProhibited / ClientRenewProhibited have no effect on auto-renews. Status is automatically set by the system when the max renewal period is reached. All grace periods are applicable and have an impact on billing: addgrace renewgrace autorenewgrace Copyright Ó 2016 DNS Belgium vzw/asbl 3

4 transfergrace Domain transfer Transfers may be done at all times. (Losing Registrar may refuse a transfer within 60 days of registration or another transfer). Contacts are cloned and get a new id which is selected by the system. The gaining registrar can check the new contact handles using infodomain after the transfer. The authinfo will be changed automatically on transfer for security reasons. The gaining registrar can check the new authinfo using infodomain. No transfer within 60 days of registration or another transfer: this is enforced by the registry by setting the servertransferprohibited flag. Contact objects remain attached to the domain. The gaining registrar can view them but can't modify them. Best practice: the gaining registrar updates the domain and attaches new contacts. The authinfo stays valid until it is changed by the sponsoring registrar. Authentication/Security DNS Belgium has the same password policy throughout the system: At least one uppercase character [A-Z]. At least one lowercase character [a-z]. At least one numerical character [0-9]. At least one non-alphanumerical character [!"#$%&'()*+,-./:;;<=>?@[]^_` { }] For the EPP password, the length of the password is according to the RFC: 8-16 characters. For web passwords and authinfo associated with domains, we allow 8-32 characters. EPP and web passwords: 8-16 Lower case letters (a-z) Upper case letters (A-Z) Numbers (0-9) Special characters (!"#$%&'()*+,-./:;;<=>?@[\]^_`{ }~) at least three of the four categories authinfo: 8-32 at least one alphanumeric character ( A to Z ;; both lower and uppercase letters), at least one numeric character ( 0 9 ) as well as or one special character. 2.2 Commonalities Following business rules are identical before and after migration: Domain creation: o Multi-year registrations with auto-renew and renew command. Domain deletion: o Deletes are effective immediately and the domain goes in redemption. Copyright Ó 2016 DNS Belgium vzw/asbl 4

5 o Domain end-of-live is fully ICANN compliant: 30 days redemption (restore possible). + 5 days pendingdelete (no restore possible). no transfer possible during redemptionperiod. Change registrant of a domain name: o Allowed by using update-domain. Contact updates: o All changes are allowed. 3 EPP 3.1 Differences Following EPP actions are different before and after migration. Action New Old Session management DNS Belgium allows 4 simultaneous EPP sessions (connections) per registrar with our EPP server. When you open more connections, the oldest connection will be closed automatically. Max 4 simultaneous sessions allowed. On 5 sessions, the new session is closed. Greeting Session timeout is 240 seconds. <?xml version="1.0" encoding="utf-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <!--Your IP is [ ]--> <greeting> <svid>epp.dnsbelgium.be</svid> <svdate> t12:40:18.989z</svdate> Session timeout is 240 seconds or transactions. <?xml version="1.0" encoding="utf-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=" <greeting> <svid>test-brussels</svid> <svdate> t12:39: z</svdate> <svcmenu> Copyright Ó 2016 DNS Belgium vzw/asbl 5

6 Login Poll <svcmenu> <version>1.0</version> <lang>en</lang> <objuri>urn:ietf:params:xml:ns:epp-1.0</objuri> <objuri>urn:ietf:params:xml:ns:domain-1.0</objuri> <objuri>urn:ietf:params:xml:ns:contact-1.0</objuri> <svcextension> <exturi>urn:ietf:params:xml:ns:secdns- 1.1</extURI> <exturi>urn:ietf:params:xml:ns:rgp-1.0</exturi> </svcextension> </svcmenu> <dcp> <access> <all/> </access> <statement> <purpose> <admin/> <prov/> </purpose> <recipient> <ours/> <public/> </recipient> <retention> <stated/> </retention> </statement> </dcp> </greeting> </epp> At least one extension should be mentioned in the login. It is possible to use commands even if the extension wasn't mentioned during login. There is no follow-up for unacknowledged poll messages. The poll command is the only way to receive server-generated messages. DNS Belgium recommends to check poll messages at least daily. <version>1.0</version> <lang>en</lang> <objuri>urn:ietf:params:xml:ns:domain-1.0</objuri> <objuri>urn:ietf:params:xml:ns:contact-1.0</objuri> <objuri>urn:ietf:params:xml:ns:host-1.0</objuri> <svcextension> <exturi>urn:ietf:params:xml:ns:secdns-1.1</exturi> <exturi>urn:ietf:params:xml:ns:rgp-1.0</exturi> <exturi>urn:ietf:params:xml:ns:launch-1.0</exturi> <exturi>urn:ietf:params:xml:ns:signedmark-1.0</exturi> <exturi>urn:ietf:params:xml:ns:mark-1.0</exturi> </svcextension> </svcmenu> <dcp> <access> <all/> </access> <statement> <purpose> <admin/> <prov/> </purpose> <recipient> <ours/> <public/> </recipient> <retention> <stated/> </retention> </statement> </dcp> </greeting> </epp> Extensions used during the session should be mentioned in login. Poll messages that are not picked up within 24 hours, are sent to the notification address. Copyright Ó 2016 DNS Belgium vzw/asbl 6

7 Create/ Update domain Hosts: host attributes. Because DNS Belgium uses host attributes, some further explanation is needed on changes when glue records are involved: 1. When the name server is in the rem section and no glue is provided: remove the name server together with all its glue records. 2. When the name server is in the rem section and glue records are provided: remove specific glue records. 3. When all glue records are provided together with the name server in the rem section: remove the name servers. Hosts: host objects. Info domain Info domain - Example Authorization: Dates: The authinfo must be provided for anyone other than the sponsoring registrar. If the authinfo is given, it must be correct. Dates in the response are rounded to the millisecond. Message counter: Hosts: There is no msgq. Host attributes. <?xml version="1.0" encoding="utf-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-"xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> <response> <result code="1000"> <msg>command completed successfully</msg> </result> <resdata> <domain:infdata> <domain:name>test.vlaanderen</domain:name> <domain:roid>d vlaander</domain:roid> <domain:status s="ok"/> Authorization: Dates: No authorization required. When the performing registrar is the sponsoring registrar or when valid authinfo is provided, the authinfo is also returned. When invalid authinfo is provided, the server responds with a 2202 response code. Dates in the response are rounded to the microsecond. Message counter: Hosts: Each response has a msgq. Host objects. <?xml version="1.0" encoding="utf-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"xmlns:xsi=" <response> <result code="1000"> <msg>command completed successfully</msg> </result> <msgq count="11" id=" "/> <resdata> <domain:infdata xmlns="urn:ietf:params:xml:ns:domain-" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> <domain:name>test.vlaanderen</domain:name> <domain:roid>d vlaander</domain:roid> Copyright Ó 2016 DNS Belgium vzw/asbl 7

8 <domain:registrant>jojo </domain:registrant> <domain:contact type="admin">jojo </domain:contact> <domain:contact type="tech">jojo </domain:contact> <domain:ns> <domain:hostattr> <domain:hostname>ns1.test.vlaanderen</domain:hostname> <domain:hostaddr ip="v4"> </domain:hostaddr> </domain:hostattr> </domain:ns> <domain:clid>testregistrar</domain:clid> <domain:crid>testregistrar</domain:crid> <domain:crdate> t07:10:38.598z</domain:crdate> <domain:upid>registry</domain:upid> <domain:update> t07:14:00.313z</domain:update> <domain:exdate> t07:10:38.598z</domain:exdate> <domain:trdate> t07:14:00.209z</domain:trdate> <domain:authinfo> <domain:pw>661:g5gqy1i"1m6iri,34<wfi<8}]82<</domain:pw> </domain:authinfo> </domain:infdata> </resdata> <trid> <cltrid>abc-12345</cltrid> <svtrid>5c207ce3-a e-9d83-a40958a911db</svtrid> </trid> </response> </epp> <domain:status s="ok"/> <domain:registrant>jojo </domain:registrant> <domain:contacttype="admin">jojo </domain:contact> <domain:contacttype="tech">jojo </domain:contact> <domain:ns> <domain:hostobj>ns1.dns.brussels</domain:hostobj> </domain:ns> <domain:host>ns1.dns.brussels</domain:host> <domain:host>ns3.dns.brussels</domain:host> <domain:clid>testregistrar</domain:clid> <domain:crid>testregistrar</domain:crid> <domain:crdate> t12:50: z</domain:crdate> <domain:upid>testregistrar</domain:upid> <domain:update> t13:54: z</domain:update> <domain:exdate> t00:00: z</domain:exdate> <domain:authinfo> <domain:pw>r#lw%x+s7u</domain:pw> </domain:authinfo> </domain:infdata> </resdata> <trid> <cltrid>abc-12345</cltrid> <svtrid> testregistrar-vlaanderen</svtrid> </trid> </response> </epp> Create/Update contact Info contact postalinfo: Required attribute type= loc or int. When using type int, only ASCII may be used. When using type loc, non ASCII characters may be used. Authorization: The authinfo must be provided for anyone other than the sponsoring registrar. If the authinfo is given, it must be correct. postalinfo: In contact objects, only the internationalized (type= int ) fields can be used. Authorization: No authorization required. When the performing registrar is the sponsoring registrar or when valid authinfo is provided, the authinfo is also returned. When invalid authinfo is provided, the server responds with a 2202 response code. Copyright Ó 2016 DNS Belgium vzw/asbl 8

9 Dates: Dates in the response are rounded to the millisecond. Message counter: There is no msgq. Dates: Dates in the response are rounded to the microsecond. Message counter: Each response has a msgq. Info contact - Example <?xml version="1.0" encoding="utf-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <response> <result code="1000"> <msg>command completed successfully</msg> </result> <resdata> <contact:infdata> <contact:id>dago </contact:id> <contact:roid>c vlaander</contact:roid> <contact:status s="ok"/> <contact:postalinfo type="int"> <contact:name>philip Dubois</contact:name> <contact:org>dns Belgium</contact:org> <contact:addr> <contact:street> Philipssite 5 bus 13</contact:street> <contact:city>leuven</contact:city> <contact:sp/> <contact:pc>3001</contact:pc> <contact:cc>be</contact:cc> <?xml version="1.0" encoding="utf-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=" <response> <result code="1000"> <msg>command completed successfully</msg> </result> <msgq count="8" id=" "/> <resdata> <contact:infdata xmlns="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <contact:id>dago </contact:id> <contact:roid>c vlaander</contact:roid> <contact:status s="linked"/> <contact:status s="ok"/> <contact:postalinfo type="int"> <contact:name>philip Dubois</contact:name> <contact:org>dns Belgium</contact:org> <contact:addr> <contact:street>philipssite 5 bus 13</contact:street> <contact:city>leuven</contact:city> <contact:pc>3001</contact:pc> Copyright Ó 2016 DNS Belgium vzw/asbl 9

10 </contact:addr> </contact:postalinfo> <contact:clid>testregistrar</contact:clid> <contact:crid>testregistrar</contact:crid> <contact:crdate> t07:02:55.568z</contact:crdate> <contact:authinfo> <contact:pw/> </contact:authinfo> </contact:infdata> </resdata> <trid> <cltrid>abc-12345</cltrid> <svtrid>0789ac12-6b c74fa9b48d38</svtrid> </trid> <contact:cc>be</contact:cc> </contact:addr> </contact:postalinfo> <contact:clid>testregistrar</contact:clid> <contact:crid>testregistrar</contact:crid> <contact:crdate> t11:53: z</contact:crdate> </contact:infdata> </resdata> <trid> <cltrid>abc-12345</cltrid> <svtrid> testregistrar-vlaander</svtrid> </trid> </response> </epp> </response> </epp> Check domain Request: Max number to check: 5 IDN domain names: U-label or A-label in request. A-label in response. Unsupported IDN character returns Invalid. Response: Status: Uses true and false. Reason: Registered, Reserved. Errors: all errors return Invalid (unsupported tld, invalid U-label, invalid A-label, etc.). Request: Max number to check: 5 IDN domain names: A-label only. Response: Status: Uses 0 and 1. Reason: Object exists, Reservation. Errors: Errors are specified: e.g. Unsupported TLD, Invalid A-Label, Invalid U-Label. Copyright Ó 2016 DNS Belgium vzw/asbl 10

11 Check contact Transfer domain - period Error responses Protected transactions threshold Request: Max number to check: 5 Response: Status: Uses true and false. Only validity period allowed: <domain:period unit="y">1</domain:period>. Months are not accepted. If the maximum registration period of 10 years is exceeded by the transfer request, the request is accepted but the period is not extended. Example error response: <?xml version="1.0" encoding="utf-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="2302"> <msg>object exists</msg> <extvalue> <value> <epp>error</epp> </value> <reason>given domain [transfer.vlaanderen] already exists.</reason> </extvalue> </result> <trid> <svtrid>703a0b89-49ac-44ed-b9d3-15a101abf524</svtrid> </trid> </response> </epp> When the threshold for protected transactions is reached, the server responds with a 2308 response code. Request: Max number to check: 5 Response: Status: Uses 0 and 1. Periods between 1 year and 10 years (included) are accepted. Default period is 1 year. Months are not accepted. transfer requests are rejected when the given period could result in a validity period exceeding 10 years, unless the transfer is requested with a period of 1 year. Example error response: <?xml version="1.0" encoding="utf-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=" <response> <result code="2302"> <msg>object exists</msg> <extvalue> <value> <exception>domainalreadyexists</exception> </value> <reason>domain [transfer.vlaanderen]: Cannot create already existing domain.</reason> </extvalue> </result> <trid> <svtrid> a-test5- brussels</svtrid> </trid> </response> </epp> NA Copyright Ó 2016 DNS Belgium vzw/asbl 11

12 3.2 Commonalities Following EPP actions are identical before and after migration: Logout: o Session is closed after logout. Create/Renew domain Period: o Periods between 1 year and 10 years (included) are accepted. o Default period is 1 year. o Months are not accepted. Create/Update domain DNSSEC: o The EPP interface accepts DS records only. A maximum of 6 DS records can be provisioned per domain. o When maxsiglife is provided by the registrar, we will return a 2102 Unimplemented option. Create/Update domain contacts: o A domain object should have at least one contact of type registrant, at least one contact of type admin, and at least one contact of type technical. o In total, a domain object may have a maximum of 10 contacts. o The contact of type bill is not supported. Create/Update domain hosts: o IDN in hosts: only A-labels are accepted, all characters are allowed. o Number of hosts allowed: 0-13 o Create/Update contact authinfo: o authinfo should be empty on creating/updating of the contact. Copyright Ó 2016 DNS Belgium vzw/asbl 12

13 4 Registrar panel 4.1 Differences Following web actions are different before and after migration. Action New Old Transactions No domain/contact transactions available EPP transactions can be done via the web interface. Protected transactions DNS Belgium implements protected transactions. More information can be found in the General manual. NA Authentication DNS Belgium implements 2 factor verification on the registrar website. More information can be found in the Web manual. Password validity is restricted in time: 180 days for master user password. 90 days for other users. Search DNS Belgium provides a search of domain names in your own portfolio. Search consists of a link to the Whois: Statistics & Reports NA search domain search contact search host Following statistics and reports are available: Domain count Domain development Ticket statistics Object list export Object queries Billing DNS Belgium only provides billing lines, which can be consulted per month. Following billing information is available: Credit management Billing lines Copyright Ó 2016 DNS Belgium vzw/asbl 13

14 Configuration Following items can be viewed/configured: Main contact data Public contact data Registrar contacts: Tech, Admin and Abuse. EPP password EPP IP addresses Registrar admin/tech/abuse contact Following items are not implemented: Registrar billing contact: Your billing contact can be changed by sending an to support. Notification address: will not be used in our system. Only EPP Poll will be used. There will be no follow up of unacknowledged poll messages. Announce addresses: Can be maintained via our.be platform. Following items can be viewed/configured: Main contact data Registrar contacts Public contact data Notification address EPP password EPP IP addresses Announce addresses 5 DAS & WHOIS 5.1 Differences Following web actions are different before and after migration. Action New Old Domain availability check There is no separate domain availability service. Registrars should use check-domain via EPP. With the finger service, you can check the availability of a domain name. command line WHOIS The command-line whois is according to ICANN requirements. All labels are shown, including those with empty value. ROID of contacts is according to ICANN requirements. The ROID is not according to ICANN requirements: ROID = handle + -TLD (not according to icann specs) Copyright Ó 2016 DNS Belgium vzw/asbl 14

15 5.2 Commonalities Following actions are identical before and after migration: The whois via the DNS Belgium website does not change. The mandatory web whois as described by ICANN does not change. 6 Registry actions with visibilty to the registrar/registrant 6.1 Differences Following internal actions are different before and after migration. Action New Old Threshold for protected transactions Domain actions - Undelete domain Block registrar EPP IP addresses DNS Belgium can reset/change the threshold. When DNS Belgium deletes a domain name, it is possible to undo it during the pendingdelete period. DNS Belgium implements a registrar lifecycle with 4 states. Initial > Active <> Blocked > Deleted It is possible to block a registrar that is in breach of contract. This registrar can t do any actions on the registry system. Only the registrar can add/delete IP addresses for EPP. DNS Belgium can view IP addresses. NA There is no undo of the delete possible in the pendingdelete period. There is no registrar lifecycle. Registrars who are in breach can be blocked by setting: EPP enabled to No credits to 0 (zero) The registry can add/delete IP addresses as well as the registrar. Copyright Ó 2016 DNS Belgium vzw/asbl 15

16 6.2 Commonalities Following internal actions are identical before and after migration: Update EPP status on domain: o The registry can update all EPP statuses of a domain name. URS procedure o The URS procedure is implemented according to ICANN requirements. EPP IP addresses o IP addresses are valid for all registrars. Copyright Ó 2016 DNS Belgium vzw/asbl 16

Quick start guide Version February Quick start guide. Release 3.1. Copyright 2015 DNS Belgium vzw

Quick start guide Version February Quick start guide. Release 3.1. Copyright 2015 DNS Belgium vzw Quick start guide Version 3.1 5 February 2016 Quick start guide Release 3.1 Copyright 2015 DNS Belgium vzw Table of contents TABLE OF CONTENTS... 2 1 INTRODUCTION... 3 1.1 Purpose... 3 1.2 Overview...

More information

VNNIC EPP GATEWAY SPECIFICATION (Version 4.2)

VNNIC EPP GATEWAY SPECIFICATION (Version 4.2) VIETNAM INTERNET NETWORK INFORMATION CENTER - VNNIC TECHNICAL DEPARTMENT VNNIC EPP GATEWAY SPECIFICATION (Version 4.2) 1 Contents Part 1. Overview... 5 1.1. Document using... 5 1.2. Release note... 5 1.3.

More information

VNNIC EPP GATEWAY SPECIFICATION (Version 4.4)

VNNIC EPP GATEWAY SPECIFICATION (Version 4.4) VIETNAM INTERNET NETWORK INFORMATION CENTER - VNNIC TECHNICAL DEPARTMENT VNNIC EPP GATEWAY SPECIFICATION (Version 4.4) 1 Contents Part 1. Overview... 5 1.1. Document using... 5 1.2. Release note... 5 1.3.

More information

IT Department Documentation. EPP Server. Protocol description. Document number: YYYY-N Last saved: 12 februari 2009

IT Department Documentation. EPP Server. Protocol description. Document number: YYYY-N Last saved: 12 februari 2009 Document number: YYYY-N Last saved: 12 februari 2009 The Internet Infrastructure Foundation (.SE) 2009 Document control Document information and security Made by Responsible for fact Responsible for document

More information

Obsoletes: 3731 May 2007 Category: Standards Track. Extensible Provisioning Protocol (EPP) Domain Name Mapping

Obsoletes: 3731 May 2007 Category: Standards Track. Extensible Provisioning Protocol (EPP) Domain Name Mapping Network Working Group S. Hollenbeck Request for Comments: 4931 VeriSign, Inc. Obsoletes: 3731 May 2007 Category: Standards Track Extensible Provisioning Protocol (EPP) Domain Name Mapping Status of This

More information

gtld Registrar Manual Part I : Quickstart

gtld Registrar Manual Part I : Quickstart gtld Registrar Manual Part I : Quickstart Version 1.0 Copyright Ó 2016 DNS Belgium vzw/asbl 1 Table of contents Table of contents... 2 1 Introduction... 3 1.1. Purpose... 3 1.2. Overview... 3 1.3 Document

More information

IT Department Documentation. EPP Server. Protocol description. Document number: 2011-N. The Internet Infrastructure Foundation (.

IT Department Documentation. EPP Server. Protocol description. Document number: 2011-N. The Internet Infrastructure Foundation (. IT Department Documentation EPP Server Protocol description Document number: 2011-N The Internet Infrastructure Foundation (.SE) IT Department Documentation EPP Server Protocol description Document control

More information

Technical Integration Guide

Technical Integration Guide TECHNICAL INTEGRATION GUIDE February 27th, 2015 1 Technical Integration Guide - Version 3.0 - February 27th, 2015-1 - TECHNICAL INTEGRATION GUIDE February 27th, 2015 2 T a b l e o f c o n t e n t 1. Preface...

More information

Textual improvements made to 4.3 Contact create. First version of the document.

Textual improvements made to 4.3 Contact create. First version of the document. 3.2 Domain info amended in line with the introduction of the option of looking up the details of domain names managed by other registrars. That option has been made available where the user is in possession

More information

DNRS2 Registrar Operations Test & Evaluation (OT&E) Version July, 2017

DNRS2 Registrar Operations Test & Evaluation (OT&E) Version July, 2017 DNRS2 Registrar Operations Test & Evaluation (OT&E) Page 1 of 77 DNRS2 Registrar Operations Test & Evaluation (OT&E) Version 1.8 03 July, 2017 Contents 1 Introduction... 3 1.1 Purpose... 3 1.2 Formatting

More information

EPP Fee Extension Protocol Instructions

EPP Fee Extension Protocol Instructions EPP Fee Extension Protocol Instructions (English version) LAST REVISION DATE: 25 October, 2016 The registration system of Beijing TeleInfo Network Technology Co., Ltd. (Teleinfo) supports Fee Extension

More information

Automated DNSSEC Provisioning

Automated DNSSEC Provisioning SWITCH, Werdstrasse 2, P.O. Box, CH-8021 Zürich www.nic.ch Automated DNSSEC Provisioning Guidelines for CDS processing at SWITCH SWITCH Version 1.0, 18 September 2018 Content 1 Introduction... 2 2 Instructions

More information

REFERENCE MANUAL (1.23)

REFERENCE MANUAL (1.23) Registry-Registrar System (1.0) REFERENCE MANUAL (1.23) June 2012 Copyright 2006, Israel Internet Association (ISOC-IL) All rights reserved. Israel Internet Association (ISOC-IL) 6 Bareket St., POB 7210,

More information

EPP Fee Extension. Gavin Brown, CentralNic gavinbrown.xyz

EPP Fee Extension. Gavin Brown, CentralNic gavinbrown.xyz EPP Fee Extension Gavin Brown, CentralNic gavin.brown@centralnic.com gavinbrown.xyz Background CentralNic pricing extension (2009) New gtld Application Round (2012-) Fee extension in development from 2013

More information

Request for Comments: 5076 Category: Standards Track December 2007

Request for Comments: 5076 Category: Standards Track December 2007 Network Working Group B. Hoeneisen Request for Comments: 5076 SWITCH Category: Standards Track December 2007 Status of This Memo ENUM Validation Information Mapping for the Extensible Provisioning Protocol

More information

gtld Registrar Manual Part III : Registrar Web

gtld Registrar Manual Part III : Registrar Web gtld Registrar Manual Part III : Registrar Web Copyright Ó 2016 DNS Belgium vzw/asbl 1 Table of contents Table of contents... 2 1 Introduction... 3 1.1. Purpose... 3 2 User management... 3 2.1 Login...

More information

Registration Guidelines. for.be

Registration Guidelines. for.be Registration Guidelines for.be Version 13.0 Part II: EPP-XML 2 april 2014 1 TABLE OF CONTENTS PART II: EPP-XML TABLE OF CONTENTS... 2 INTRODUCTION... 3 USERID AND PASSWORD... 3 IP ADDRESSES... 3 ABOUT

More information

Version Author Date Comment. 1.0 Viestintävirasto Update to Contact object; type, role, isfinnish, org, form, name.

Version Author Date Comment. 1.0 Viestintävirasto Update to Contact object; type, role, isfinnish, org, form, name. 1 (50) EPP interface Version Author Date Comment 1.0 Viestintävirasto 21.9.2015 1.0 Viestintävirasto 21.10.2015 Update to Contact object; type, role, isfinnish, org, form, name. Disclose voice unsupported

More information

Contact Object Usage Patterns

Contact Object Usage Patterns Contact Object Usage Patterns Gavin Brown CTO, CentralNic gavin.brown@centralnic.com Introduction Standard Data Model for Domain Registries: RFC series 5731 5733 Three "first-class" object types: Domains

More information

Onboard with GoDaddy Questionnaire

Onboard with GoDaddy Questionnaire Onboard with GoDaddy Questionnaire Please answer the questions below for each of your TLDs, choosing from the response options noted to the right of the question and adding additional detail where reques

More information

NEUSTAR REGISTRAR REFERENCE GUIDE SUNRISE SUPPLEMENT: FIRST COME, FIRST SERVED AWARD METHOD

NEUSTAR REGISTRAR REFERENCE GUIDE SUNRISE SUPPLEMENT: FIRST COME, FIRST SERVED AWARD METHOD NEUSTAR REGISTRAR REFERENCE GUIDE SUNRISE SUPPLEMENT: FIRST COME, FIRST SERVED AWARD METHOD December 20, 2013 This document is for informational purposes only. NEUSTAR MAKES NO WARRANTIES, EXPRESS, IMPLIED,

More information

The Domain Name Registration Policy

The Domain Name Registration Policy The Domain Name Registration Policy version 3.2 developed jointly with Hostmaister LLC by public domain administrators and registrars on November 1, 2013 and changes from LLC "PE Coordinator" October 1,

More information

SWITCH, Werdstrasse 2, P.O. Box, CH-8021 Zürich EPP Manual. Version with DNSSEC and RGP. July 12, 2017 SWITCH

SWITCH, Werdstrasse 2, P.O. Box, CH-8021 Zürich  EPP Manual. Version with DNSSEC and RGP. July 12, 2017 SWITCH EPP Manual Version 2.1.6 with DNSSEC and RGP July 12, 2017 SWITCH Contents 1 Management Summary... 3 2 Introduction... 3 2.1 EPP standard + legal fundaments... 4 2.2 Conditions of use... 4 3 Using the

More information

EPP Extension Discussion

EPP Extension Discussion EPP Extension Discussion Allocation Token Extension Change Poll Extension IDN Table Mapping James F. Gould March 22, 2015 Introduction Discuss Three EPP Extension Internet Drafts with Why What Open Items

More information

Registrar- web Version February Registrar- web. Release 3.1. Copyright 2015 DNS Belgium vzw

Registrar- web Version February Registrar- web. Release 3.1. Copyright 2015 DNS Belgium vzw Registrar- web Version 3.1 5 February 2016 Registrar- web Release 3.1 Copyright 2015 DNS Belgium vzw Table of contents 1 Registrar Web... 3 1.1 User Management... 3 1.1.1 Permissions... 3 1.1.2 Transactions...

More information

<contact:authinfo> <contact:pw>2foobar</contact:pw> </contact:authinfo> <contact:disclose flag="0"> <contact:voice/> <contact: /> </contact:disclo

<contact:authinfo> <contact:pw>2foobar</contact:pw> </contact:authinfo> <contact:disclose flag=0> <contact:voice/> <contact: /> </contact:disclo PHP EPP Connection This lab requires one to have Apache webserver Copy the client folder to the webroot of your web server To test whether your registry is ready for epp connections : openssl s_client

More information

Management of synchronous operations on domain names of the cctld.it

Management of synchronous operations on domain names of the cctld.it Management of synchronous operations on domain names of the cctld.it Guidelines Version 1.4 July 11, 2012 CONTENTS 1 Synchronous registration system of the Italian Registry 1 2 Objectives of the Guidelines

More information

DOMAIN NAME LIFECYCLE POLICY FOR THE TLDS.KOELN /.COLOGNE

DOMAIN NAME LIFECYCLE POLICY FOR THE TLDS.KOELN /.COLOGNE DOMAIN NAME LIFECYCLE POLICY FOR THE TLDS.KOELN /.COLOGNE A. Purpose of this document The purpose of this policy is to describe the various states that a domain name may be in during its life. B. Registration

More information

Domain Name Lifecycle Policy

Domain Name Lifecycle Policy 5 June 2017 CURRENT dotshabaka Registry dotshabaka.com @dotshabaka دوت شبكة ريجستري اسماء.شبكة @dotshabaka International Domain Registry Pty Ltd trading as dotshabaka Registry ACN 156 339 874 ABN 71 156

More information

Onboarding guide for new gtlds operated by Afnic

Onboarding guide for new gtlds operated by Afnic ONBOARDING GUIDE FOR NEW GTLDS OPERATED BY AFNIC July 23 rd, 2013 1 Onboarding guide for new gtlds operated by Afnic.alsace,.aquitaine,.bzh,.corsica,.paris - Version 1 - July 23rd, 2013 ONBOARDING GUIDE

More information

Appendix A. Proposed Service. Name of Proposed Service: Technical description of Proposed Service: Technical Bundle for.ngo and.

Appendix A. Proposed Service. Name of Proposed Service: Technical description of Proposed Service: Technical Bundle for.ngo and. Appendix A ICANN Registry Request Service Proposed Service Name of Proposed Service: Technical Bundle for.ngo and.ong New gtlds Technical description of Proposed Service: Public Interest Registry intends

More information

RDAP Operational Profile for gtld Registries and Registrars. 3 December 2015 Version: 1.0 Status: Draft

RDAP Operational Profile for gtld Registries and Registrars. 3 December 2015 Version: 1.0 Status: Draft RDAP Operational Profile for gtld Registries and Registrars 3 December 2015 Version: 1.0 Status: Draft 1. Contents 1. CONTENTS... 2 2. INTRODUCTION... 3 3. RDAP OPERATIONAL PROFILE... 4 APPENDIX A: OPEN

More information

Extensible Provisioning Protocol (EPP) v1.6 ORG DNSSEC Registrar Acceptance Criteria

Extensible Provisioning Protocol (EPP) v1.6 ORG DNSSEC Registrar Acceptance Criteria Extensible Provisioning Protocol (EPP) v1.6 ORG DNSSEC Registrar Acceptance Criteria May 2010 v1.6 PIR Technical Support Web: http://www.pir.org E-mail: techsupport@pir.org Telephone: +1.416.646.3308 Contents

More information

Author: Trond Haugen Resp: Jarle Greipsland Date: Rev: 2e2. UNINETT Norid. EPP_Interface_Specification.odt

Author: Trond Haugen Resp: Jarle Greipsland Date: Rev: 2e2. UNINETT Norid. EPP_Interface_Specification.odt UN2007--023 1 (26) UNINETT Norid EPP Interface ification This document specifies the EPP interface to the Norid EPP Registry System. UN2007--023 Document History 2 (26) Date Revision Author Comment 2007-12-13

More information

UN2007-Spec-023 Author: Trond Haugen Resp: Jarle Greipsland Date: Rev: 5p3. UNINETT Norid. EPP_Interface_Specification.

UN2007-Spec-023 Author: Trond Haugen Resp: Jarle Greipsland Date: Rev: 5p3. UNINETT Norid. EPP_Interface_Specification. UN2007--023 1 (36) UNINETT Norid EPP Interface ification This document specifies the EPP interface to the Norid EPP Registry System. UN2007--023 Document History 2 (36) Date Revision Author Comment 2007-12-13

More information

Management of operations on domain names of the cctld.it Technical Guidelines Version 2.1. Management of operations on domain names of the cctld.

Management of operations on domain names of the cctld.it Technical Guidelines Version 2.1. Management of operations on domain names of the cctld. Management of operations on domain names of the cctld.it Technical Guidelines Version 2.1 November 3, 2014 CONTENTS 1 Revisions 1 2 Registration system of the Italian Registry 3 2.1 Introduction 3 2.2

More information

Registration Guidelines. for.be

Registration Guidelines. for.be Registration Guidelines for.be Part III: Registrar site 18 October 2018 1 TABLE OF CONTENTS Part III: WEB interface TABLE OF CONTENTS...2 MY REGISTRATIONS...4 LOG IN...4 GENERAL FORMAT...5 PROFILE MANAGEMENT

More information

Extensible Provisioning Protocol (EPP) v1.4.cctld Registrar Acceptance Criteria

Extensible Provisioning Protocol (EPP) v1.4.cctld Registrar Acceptance Criteria Extensible Provisioning Protocol (EPP) v1.4.cctld Registrar Acceptance Criteria Published June 3, 2011 Version 1.4.0.ccTLD Technical Support: techsupport@afilias-grs.info +1.416.646.3309 URL: http://www.afilias-grs.info

More information

Internet Engineering Task Force (IETF) Request for Comments: 8543 Category: Standards Track. J. Yao CNNIC. J. Gould VeriSign, Inc. G.

Internet Engineering Task Force (IETF) Request for Comments: 8543 Category: Standards Track. J. Yao CNNIC. J. Gould VeriSign, Inc. G. Internet Engineering Task Force (IETF) Request for Comments: 8543 Category: Standards Track ISSN: 2070-1721 L. Zhou CNNIC N. Kong Consultant J. Yao CNNIC J. Gould VeriSign, Inc. G. Zhou March 2019 Abstract

More information

Extensible Provisioning Protocol (EPP) v1.0 Registrar Acceptance Criteria

Extensible Provisioning Protocol (EPP) v1.0 Registrar Acceptance Criteria Extensible Provisioning Protocol (EPP) v1.0 Registrar Acceptance Criteria Published December 10th, 2013 Version 1.7.2 Technical Support: Portal: https://registrars.afilias.tld/cgi-bin/ssl/open_update_ticket.cgi

More information

.BIZ Agreement Appendix 10 Service Level Agreement (SLA) (22 August 2013)

.BIZ Agreement Appendix 10 Service Level Agreement (SLA) (22 August 2013) .BIZ Agreement Appendix 10 Service Level Agreement (SLA) (22 August 2013) Registry Operator and ICANN agree to engage in good faith negotiations to replace this Appendix 10 with a Service Level Agreement

More information

FRED open source registry system..cz.nic, z.s.p.o >Jaromír Talíř /

FRED open source registry system..cz.nic, z.s.p.o >Jaromír Talíř / FRED open source registry system.cz.nic, z.s.p.o >Jaromír Talíř >jaromir.talir@nic.cz 2008.4.8 /http://www.nic.cz http://fred.nic.cz 1 Agenda History and overview )Primary features )registration process

More information

DNSSEC Abridged Test Extensible Provisioning Protocol (EPP) v1.9.2.org Registrar Acceptance Criteria

DNSSEC Abridged Test Extensible Provisioning Protocol (EPP) v1.9.2.org Registrar Acceptance Criteria DNSSEC Abridged Test Extensible Provisioning Protocol (EPP) v1.9.2.org Registrar Acceptance Criteria Published March 13, 2014 Version 1.9.2 Technical Support: techsupport@pir.org / +1.416.646.3306 http://www.pir.org

More information

Intended status: Standards Track Expires: December 30, 2017 June 28, 2017

Intended status: Standards Track Expires: December 30, 2017 June 28, 2017 Network Working Group B. Ellacott Internet-Draft T. Harrison Intended status: Standards Track APNIC Pty Ltd Expires: December 30, 2017 June 28, 2017 Abstract History of records in the Registration Data

More information

Proposed Service. Name of Proposed Service: Technical description of Proposed Service: Redemption Grace Period for.name.

Proposed Service. Name of Proposed Service: Technical description of Proposed Service: Redemption Grace Period for.name. Proposed Service Name of Proposed Service: Redemption Grace Period for.name Technical description of Proposed Service: Background Domain-name registrations can be deleted from TLD registries without a

More information

Contractual Compliance. Text. IPC Meeting. Tuesday, 24 June 2014 #ICANN50

Contractual Compliance. Text. IPC Meeting. Tuesday, 24 June 2014 #ICANN50 Contractual Compliance IPC Meeting Tuesday, 24 June 2014 Contractual Compliance Update Since ICANN 49 Ongoing efforts and alignment on 2013 RAA and the new Registry Agreement Launched a quality process

More information

Sponsor s Monthly Report for.coop TLD

Sponsor s Monthly Report for.coop TLD Sponsor s Monthly Report for.coop TLD Reporting period: May 2011 In this report the terms dotcoop, Registry and Sponsor refer to DotCooperation LLC, the Sponsor of the dotcoop TLD. Table of Contents 1

More information

Version 2 13 October Registry.Net.Za

Version 2 13 October Registry.Net.Za - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DotCapetown Published Policies and

More information

Advisory: Clarifications to the Registry and Registrar Requirements for WHOIS (port 43) and Web-Based Directory Services

Advisory: Clarifications to the Registry and Registrar Requirements for WHOIS (port 43) and Web-Based Directory Services Advisory: Clarifications to the Registry and Registrar Requirements for WHOIS (port 43) and Web-Based Directory Services Publication date: 12 September 2014; Updated on 27 April 2015; Further Updated on

More information

CIRA Registrar Documentation..CA Registry Guide for Registrars

CIRA Registrar Documentation..CA Registry Guide for Registrars CIRA Registrar Documentation.CA Registry Guide for Registrars Version: 4.06 Release: June 3, 2011 2.CA Registry Guide for Registrars: Version 4.06 DISCLAIMER AND COPYRIGHT NOTICE Everything in this document

More information

4. Performance Specifications. 4.1 Goals and intentions of Service Level Agreements and Public Service Monitoring. Goals of Service Level Agreements:

4. Performance Specifications. 4.1 Goals and intentions of Service Level Agreements and Public Service Monitoring. Goals of Service Level Agreements: 4. Performance Specifications 4.1 Goals and intentions of Service Level Agreements and Public Service Monitoring Goals of Service Level Agreements: Service Level Agreements are set between ICANN and Registry

More information

.CAM Registry. GDPR integration. Version nd May CAM AC Webconnecting Holding B.V. Beurs plein AA Rotterdam

.CAM Registry. GDPR integration. Version nd May CAM AC Webconnecting Holding B.V. Beurs plein AA Rotterdam .CAM Registry GDPR integration Version 1.1 2 nd May 2018 Scope: This document describes the measures to be taken by.cam Registry to stay compliant with the General Data Protection Regulation (GDPR) which

More information

REGISTRATION DATA DIRECTORY SERVICE (WHOIS) SPECIFICATION

REGISTRATION DATA DIRECTORY SERVICE (WHOIS) SPECIFICATION REGISTRATION DATA DIRECTORY SERVICE (WHOIS) SPECIFICATION [Note: ICANN will be proposing updated language regarding the term Whois to comply with SSAC recommendations. The updated language will not represent

More information

Intellectual Property Constituency (IPC)

Intellectual Property Constituency (IPC) Contractual Compliance Intellectual Property Constituency (IPC) Tuesday, 14 October 2014 Agenda Registrar Related Update since ICANN 50 Registry Related Update since ICANN 50 Audit Programs Update Questions

More information

Advisory Concerning Inter-Registrar Transfer Policy. 23 August 2007

Advisory Concerning Inter-Registrar Transfer Policy. 23 August 2007 Advisory Concerning Inter-Registrar Transfer Policy 23 August 2007 The purpose of this advisory is to assist ICANN-accredited registrars and domain-name registrants in understanding how the Inter-Registrar

More information

RDAP Implementation. Francisco Arias & Gustavo Lozano 21 October 2015

RDAP Implementation. Francisco Arias & Gustavo Lozano 21 October 2015 RDAP Implementation Francisco Arias & Gustavo Lozano 21 October 2015 Agenda 1 2 3 History of Replacing WHOIS protocol gtld RDAP Profile RDAP Profile Details 4 5 Open Issues gtld RDAP Profile Conclusion

More information

Sponsor s Monthly Report for.coop TLD

Sponsor s Monthly Report for.coop TLD Sponsor s Monthly Report for.coop TLD Reporting period: November In this report the terms dotcoop, Registry and Sponsor refer to DotCooperation LLC, the Sponsor of the dotcoop TLD. Table of Contents 1

More information

Extensible Provisioning Protocol (EPP) v3.0.in Registrar Acceptance Criteria

Extensible Provisioning Protocol (EPP) v3.0.in Registrar Acceptance Criteria Extensible Provisioning Protocol (EPP) v3.0.in Registrar Acceptance Criteria Published May 6th, 2013 Version 3.0.IN Technical Support: techsupport@registry.in +1.416.619.3030 +91.11.4161.4045 URL: http://www.registry.in

More information

FRED open source registry solution. Jaromir Talir

FRED open source registry solution. Jaromir Talir FRED open source registry solution Jaromir Talir jaromir.talir@nic.cz Agenda CZ.NIC story FRED overview Deployments Data model Interfaces Features CZ.NIC story - year 2005 CZ.NIC had 4 employees Number

More information

PROCEDURE GUIDE. Technical and operational procedures for Internet top-level domains corresponding to the country codes for France REFERENCE DOCUMENTS

PROCEDURE GUIDE. Technical and operational procedures for Internet top-level domains corresponding to the country codes for France REFERENCE DOCUMENTS REFERENCE DOCUMENTS PROCEDURE GUIDE Technical and operational procedures for Internet top-level domains corresponding to the country codes for France REFERENCE DOCUMENTS 02 PREAMBLE 03 GLOSSARY 04 1. AVAILABILITY

More information

Inter-Registrar Transfer Policy (IRTP) Audit Report

Inter-Registrar Transfer Policy (IRTP) Audit Report Inter-Registrar Transfer Policy (IRTP) Audit Report Executive Summary This is a report on an Inter-Registrar Transfer Policy (IRTP) compliance audit that ICANN recently conducted. ICANN s Contractual Compliance

More information

Christmas Island Domain Administration Limited ( cxda)

Christmas Island Domain Administration Limited ( cxda) Christmas Island Domain Administration Limited ( cxda) HIGH RISK REGISTRATIONS IDENTIFICATION PROACTIVE ABUSE MITIGATION Tools provided by: Initial Try 2012 Mandatory manual domain activation with the

More information

Management of operations on domain names of the cctld.it Technical Guidelines Version 2.3

Management of operations on domain names of the cctld.it Technical Guidelines Version 2.3 Management of operations on domain names of the cctld.it Technical Guidelines Version 2.3 June 8, 2018 CONTENTS 1 Revisions 1 2 Registration system of the Italian Registry 4 2.1 Introduction 4 2.2 Characters

More information

Abu Dhabi Systems Information Center REGISTRATION POLICY. AUH-ASCII-POL Registration Policy - 1.0

Abu Dhabi Systems Information Center REGISTRATION POLICY. AUH-ASCII-POL Registration Policy - 1.0 Abu Dhabi Systems Information Center REGISTRATION POLICY AUH-ASCII-POL-001 - Registration Policy - 1.0 04/07/2018 عام / Public This document is provided pursuant to the disclaimer provided on the last

More information

Proposed Final Report on the Post-Expiration Domain Name Recovery Policy Development Process Executive Summary

Proposed Final Report on the Post-Expiration Domain Name Recovery Policy Development Process Executive Summary Proposed Final Report on the Post-Expiration Domain Name Recovery Policy Development Process STATUS OF THIS DOCUMENT This is the of the Proposed Final Report on the Post-Expiration Domain Name Recovery

More information

General Update Contractual Compliance Initiatives and Improvements Audit Program Update Complaints Handling and Enforcement Summary

General Update Contractual Compliance Initiatives and Improvements Audit Program Update Complaints Handling and Enforcement Summary Internet Corporation for Assigned Names and Numbers Contractual Compliance Update Contractual Compliance Update for July 2013 1 April June 2016 http://www.icann.org/en/resources/compliance Table of Contents

More information

Draft Applicant Guidebook, v3

Draft Applicant Guidebook, v3 Draft Applicant Guidebook, v3 Module 5 Please note that this is a discussion draft only. Potential applicants should not rely on any of the proposed details of the new gtld program as the program remains

More information

AutoDNS Manual Version 9.0 September InterNetX GmbH

AutoDNS Manual Version 9.0 September InterNetX GmbH USER MANUAL AutoDNS Manual Version 9.0 September 2016 1998-2016 InterNetX GmbH Text, content, design and the arrangement of this manual are subject to the protection of copyright laws. You may only use

More information

Abu Dhabi Systems Information Center REGISTRATION POLICY. AUH-IDN-POL Registration Policy - 1.0

Abu Dhabi Systems Information Center REGISTRATION POLICY. AUH-IDN-POL Registration Policy - 1.0 Abu Dhabi Systems Information Center REGISTRATION POLICY AUH-IDN-POL-001 - Registration Policy - 1.0 04/07/2018 عام / Public This document is provided pursuant to the disclaimer provided on the last page.

More information

RDAP Implementation. 7 March 2016 Francisco Arias & Gustavo Lozano ICANN 55 7 March 2016

RDAP Implementation. 7 March 2016 Francisco Arias & Gustavo Lozano ICANN 55 7 March 2016 RDAP Implementation 7 March 2016 Francisco Arias & Gustavo Lozano ICANN 55 7 March 2016 Agenda 1 2 3 Introduction [10 min] Differentiated Access [15 min] Thick Whois vs Registrar s RDAP [20 min] 4 5 Registrar

More information

Information. .SE Registry. FAQ for Registrars. December 1, 2009

Information. .SE Registry. FAQ for Registrars. December 1, 2009 Information.SE Registry December 1, 2009 SE, Stiftelsen för Internetinfrastruktur 2009 Table of contents 1 GENERAL 8 1.1 WHAT IS THE DIFFERENCE BETWEEN.SE,.SE REGISTRY AND.SE DIRECT? 8 1.2 WHAT IS MEANT

More information

Contractual Compliance

Contractual Compliance Contractual Compliance Registrars Outreach Thursday, 26 Jun 2014 Agenda General Update Quality process to periodically confirm compliance for suspended domains related to Whois Inaccuracy complaints Compliance

More information

AMENDMENT NO. 1 TO REGISTRY-REGISTRAR AGREEMENT

AMENDMENT NO. 1 TO REGISTRY-REGISTRAR AGREEMENT AMENDMENT NO. 1 TO REGISTRY-REGISTRAR AGREEMENT This Amendment No. 1 to the Registry-Registrar Agreement (this Amendment ) is made as of this 2 day of November, 2004, by and between VeriSign, Inc. ( VERISIGN

More information

Domain Name Hijacking A Preliminary Report. Security and Stability Advisory Committee Mar del Plata April 5, 2005

Domain Name Hijacking A Preliminary Report. Security and Stability Advisory Committee Mar del Plata April 5, 2005 Domain Name Hijacking A Preliminary Report Security and Stability Advisory Committee Mar del Plata April 5, 2005 1 Headlines Panix.com was hijacked on 15 Jan 2005 action returned it after 48 hours Gaining

More information

STD: 69 August 2009 Obsoletes: 4932 Category: Standards Track. Extensible Provisioning Protocol (EPP) Host Mapping

STD: 69 August 2009 Obsoletes: 4932 Category: Standards Track. Extensible Provisioning Protocol (EPP) Host Mapping Network Working Group S. Hollenbeck Request for Comments: 5732 VeriSign, Inc. STD: 69 August 2009 Obsoletes: 4932 Category: Standards Track Abstract Extensible Provisioning Protocol (EPP) Host Mapping

More information

ICANN Contractual Compliance. ALAC Mee(ng. Sunday, 23 March 2014 #ICANN49

ICANN Contractual Compliance. ALAC Mee(ng. Sunday, 23 March 2014 #ICANN49 ICANN Contractual Compliance ALAC Mee(ng Sunday, 23 March 2014 1 Agenda! Compliance General Update! Clarification of ALAC statement! Q&A session! Contractual Compliance Update! Ø Global presence in Singapore"

More information

[1] Addition of French, Spanish, and German languages to the list of approved languages for the following TLD:.xn--fjq720a

[1] Addition of French, Spanish, and German languages to the list of approved languages for the following TLD:.xn--fjq720a Proposed Service Name of Proposed Service: Addition of certain language scripts to Donuts TLDs Technical description of Proposed Service: Donuts Inc. would like to provide registration of domain names

More information

Registration Guidelines. for.be

Registration Guidelines. for.be Registration Guidelines for.be Part I: General 6 december 2018 1 Change log 18/10/2018 Removal of transaction fee for online payments 1/8/2018 Bug fixes Change in maintenance window Info-domain and info-contact

More information

ICANN Monitoring System API (MoSAPI)

ICANN Monitoring System API (MoSAPI) ICANN Monitoring System API (MoSAPI) Version 2.7 2018-03-06 1. Introduction... 3 1.1. Date and Time... 3 1.2. Credentials... 3 1.3. Glossary... 3 2. Common elements used in this specification... 5 3. Session

More information

2 INTRODUCTION REVIEW OF POLICY THE REGISTRY SYSTEM AND SERVICES CONTACT OPERATIONS NEW DOMAIN REGISTRATIONS...

2 INTRODUCTION REVIEW OF POLICY THE REGISTRY SYSTEM AND SERVICES CONTACT OPERATIONS NEW DOMAIN REGISTRATIONS... - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Net.Za Published Policies and Procedures - - - - - - - - -

More information

Registry Operator Monthly Report

Registry Operator Monthly Report Registry Operator Monthly Report July 2017 Prepared: August 2017 Neustar, Inc. 21575 Ridgetop Circle Sterling, VA 20166 As required by the Department of Commerce/Neustar Registry Agreements, this report

More information

Understanding RDAP and the Role it can Play in RDDS Policy. ICANN October 2018

Understanding RDAP and the Role it can Play in RDDS Policy. ICANN October 2018 1 Understanding RDAP and the Role it can Play in RDDS Policy ICANN 63 22 October 2018 2 Agenda Introduction RDAP Implementation Status in gtlds RDAP: Mechanism and Policy Authentication and RDAP Registrar

More information

Introduction. Prepared by: ICANN Org Published on: 12 January 2018

Introduction. Prepared by: ICANN Org Published on: 12 January 2018 Proposed Interim Models for Compliance with ICANN Agreements and Policies in Relation to the European Union s General Data Protection Regulation For Discussion Prepared by: ICANN Org Published on: 12 January

More information

Internationalizing WHOIS Preliminary Approaches for Discussion

Internationalizing WHOIS Preliminary Approaches for Discussion Internationalizing WHOIS Preliminary Approaches for Discussion Internationalized Registration Data Working Group ICANN Meeting, Brussels, Belgium Edmon Chung, Co-Chair Jeremy Hitchcock, Co-Chair 20 June

More information

.ngo.ong EPP Acceptance Criteria. With optional DNSSEC Version 1.1

.ngo.ong EPP Acceptance Criteria. With optional DNSSEC Version 1.1 .ngo.ong EPP Acceptance Criteria With optional DNSSEC Version 1.1 Table of Contents 2.1 Starting the test... 3 2.2. Session Management... 3 2.2.1 Start Session... 3 2.2.2 Authentication... 3 2.2.3 Domain

More information

Registration Guidelines. for.be

Registration Guidelines. for.be Registration Guidelines for.be Version 15.1 Part I: General 28 januari 2015 1 Change log Version 15.1 Registrar list Mails regarding abuse Version 15.0 Domain Guard change to EPP settings permissions security

More information

Internet Corporation for Assigned Names & Numbers Contractual Compliance Update

Internet Corporation for Assigned Names & Numbers Contractual Compliance Update Contractual Compliance Update for July 2013 1 Internet Corporation for Assigned Names & Numbers Contractual Compliance Update October 20 http://www.icann.org/en/resources/compliance Table of Contents 1

More information

API Documentation. Version 3.0

API Documentation. Version 3.0 API Documentation Version 3.0 Table of Contents Change History... 4 Contact Information... 5 API Connection Details... 5 API Error Handling... 5 Account Balance Query... 6 Domain Names & DNS... 7 Domain

More information

Contractual Compliance Update ICANN 52 February 2015

Contractual Compliance Update ICANN 52 February 2015 Contractual Compliance Update ICANN 52 February 2015 Agenda Update Since ICANN 51 Lessons Learned Summary Questions and Answers 3 General Update since ICANN 51 Year-three Audit Program launched in October

More information

Contractual Compliance Update. Contractual Compliance ICANN 57 5 November 2016

Contractual Compliance Update. Contractual Compliance ICANN 57 5 November 2016 Contractual Compliance Update Contractual Compliance ICANN 57 5 November 2016 Agenda Brief Update Since ICANN 55 Registrar Compliance Update Registry Compliance Update Contractual Compliance Audit Activities

More information

Version 2.4 Final. TMDB System User Manual (Registry)

Version 2.4 Final. TMDB System User Manual (Registry) Version 2.4 Final TMDB System User Manual (Registry) Table of contents 1. INTRODUCTION... 5 1.1. OVERVIEW OF THE TMDB SYSTEM... 5 1.2. THE INTENDED AUDIENCE FOR THIS DOCUMENT... 5 1.3. OVERVIEW OF THIS

More information

gtld Compliance Program Contractual Compliance

gtld Compliance Program Contractual Compliance gtld Compliance Program Contractual Compliance Contractual Compliance Process Guidelines and Clarifications Informal Resolution Process Guidelines Notice o Sent regarding an alleged area of noncompliance

More information

DRAFT: gtld Registration Dataflow Matrix and Information

DRAFT: gtld Registration Dataflow Matrix and Information DRAFT: gtld Registration Dataflow Matrix and Information Summary of Input Received From Contracted Parties and Interested Stakeholders. Version 2 6 November 2017 ICANN DRAFT: gtld Registration Dataflow

More information

ARADIAL TECHNOLOGIES Aradial Enforcer Manual Version 7.0

ARADIAL TECHNOLOGIES Aradial Enforcer Manual Version 7.0 ARADIAL TECHNOLOGIES Aradial Enforcer Manual Version 7.0 Administration Guide A R A D I A L E N F O R C E R Administration Guide Aradial Technologies Ltd. Information in this document is subject to change

More information

APTLD & MYNIC JOINT SURVEY

APTLD & MYNIC JOINT SURVEY INTERNET SECURITY & CCTLDS SURVEY RESULTS 24 th June 2008, Tuesday ccnso meeting, Paris, France Survey Objectives Survey Summary:- For APTLD members to examine the roles and responsibilities of cctlds

More information

Version 2.3 Final. TMDB System User Manual (Registrar)

Version 2.3 Final. TMDB System User Manual (Registrar) Version 2.3 Final TMDB System User Manual (Registrar) Table of contents 1. INTRODUCTION... 4 1.1. OVERVIEW OF THE TMDB SYSTEM... 4 1.2. THE INTENDED AUDIENCE FOR THIS DOCUMENT... 4 1.3. OVERVIEW OF THIS

More information

Registry Outreach. Contractual Compliance ICANN February 2015

Registry Outreach. Contractual Compliance ICANN February 2015 Registry Outreach Contractual Compliance ICANN 52 12 February 2015 Agenda Update Since ICANN 51 Registry Agreement Lessons Learned Summary & Guidelines Process Guidelines & Clarifications Policy Efforts

More information

1. Anti-Piracy Services. 2. Brand Protection (SAAS) 3. Brand Protection Services. Data Protection and Permitted Purpose. Services

1. Anti-Piracy Services. 2. Brand Protection (SAAS) 3. Brand Protection Services. Data Protection and Permitted Purpose. Services MarkMonitor Services Our operating information for all MarkMonitor products and services is outlined below. References in this document to MarkMonitor means the Clarivate entity identified in the order

More information

ICANN Naming Services portal User s Guide

ICANN Naming Services portal User s Guide ICANN Naming Services portal User s Guide ICANN Product Team 25 September 2017 ICANN ICANN Naming Services portal User s Guide September 2017 1 TABLE OF CONTENTS REVISION HISTORY 4 CONTACT US 4 1 INTRODUCTION:

More information

Post-Expiration Domain Name Recovery PDP. Presentation of Final Report

Post-Expiration Domain Name Recovery PDP. Presentation of Final Report Post-Expiration Domain Name Recovery PDP Presentation of Final Report Background To what extent should registrants be able to reclaim their domain names after they expire? Issue brought to the GNSO by

More information