centralnicregistry.com Open in urlscan Pro
2a04:2b00:212::c:250:170  Public Scan

Form analysis
0 forms found in the DOM

Text Content

We value your privacy

We use cookies to enhance your browsing experience, serve personalized ads or
content, and analyze our traffic. By clicking "Accept All", you consent to our
use of cookies.

Customize Accept All
Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions.
You will find detailed information about all cookies under each consent category
below.

The cookies that are categorized as "Necessary" are stored on your browser as
they are essential for enabling the basic functionalities of the site. ... Show
more

NecessaryAlways Active

Necessary cookies are required to enable the basic features of this site, such
as providing secure log-in or adjusting your consent preferences. These cookies
do not store any personally identifiable data.

 * Cookie
   __hssrc
 * Duration
   session
 * Description
   This cookie is set by Hubspot whenever it changes the session cookie. The
   __hssrc cookie set to 1 indicates that the user has restarted the browser,
   and if the cookie does not exist, it is assumed to be a new session.

 * Cookie
   __hssc
 * Duration
   30 minutes
 * Description
   HubSpot sets this cookie to keep track of sessions and to determine if
   HubSpot should increment the session number and timestamps in the __hstc
   cookie.

 * Cookie
   _zm_mtk_guid
 * Duration
   1 year 1 month 4 days
 * Description
   Zoom sets this cookie for the Zoom support team.

 * Cookie
   _zm_visitor_guid
 * Duration
   1 year
 * Description
   Zoom sets this cookie for the Zoom support team.

 * Cookie
   _zm_ssid
 * Duration
   session
 * Description
   Zoom sets this cookie for the Zoom support team.

 * Cookie
   _zm_ctaid
 * Duration
   2 hours
 * Description
   Zoom sets this cookie for the Zoom support team.

 * Cookie
   _zm_csp_script_nonce
 * Duration
   session
 * Description
   Zoom sets this cookie for the Zoom support team.

 * Cookie
   _zm_currency
 * Duration
   1 day
 * Description
   Zoom sets this cookie for the Zoom support team.

Functional


Functional cookies help perform certain functionalities like sharing the content
of the website on social media platforms, collecting feedback, and other
third-party features.

 * Cookie
   __cf_bm
 * Duration
   30 minutes
 * Description
   Cloudflare set the cookie to support Cloudflare Bot Management.

 * Cookie
   _hjAbsoluteSessionInProgress
 * Duration
   30 minutes
 * Description
   Hotjar sets this cookie to detect a user's first pageview session, which is a
   True/False flag set by the cookie.

 * Cookie
   _zm_chtaid
 * Duration
   2 hours
 * Description
   Zoom sets this cookie to facilitate video conferences via zoom from the
   website.

 * Cookie
   player
 * Duration
   1 year
 * Description
   Vimeo uses this cookie to save the user's preferences when playing embedded
   videos from Vimeo.

 * Cookie
   aka_debug
 * Duration
   session
 * Description
   Vimeo sets this cookie which is essential for the website to play video
   functionality.

Analytics


Analytical cookies are used to understand how visitors interact with the
website. These cookies help provide information on metrics such as the number of
visitors, bounce rate, traffic source, etc.

 * Cookie
   _ga
 * Duration
   1 year 1 month 4 days
 * Description
   Google Analytics sets this cookie to calculate visitor, session and campaign
   data and track site usage for the site's analytics report. The cookie stores
   information anonymously and assigns a randomly generated number to recognise
   unique visitors.

 * Cookie
   _gid
 * Duration
   1 day
 * Description
   Google Analytics sets this cookie to store information on how visitors use a
   website while also creating an analytics report of the website's performance.
   Some of the collected data includes the number of visitors, their source, and
   the pages they visit anonymously.

 * Cookie
   _gat_UA-*
 * Duration
   1 minute
 * Description
   Google Analytics sets this cookie for user behaviour tracking.

 * Cookie
   _hjFirstSeen
 * Duration
   30 minutes
 * Description
   Hotjar sets this cookie to identify a new user’s first session. It stores the
   true/false value, indicating whether it was the first time Hotjar saw this
   user.

 * Cookie
   __hstc
 * Duration
   5 months 27 days
 * Description
   Hubspot set this main cookie for tracking visitors. It contains the domain,
   initial timestamp (first visit), last timestamp (last visit), current
   timestamp (this visit), and session number (increments for each subsequent
   session).

 * Cookie
   hubspotutk
 * Duration
   5 months 27 days
 * Description
   HubSpot sets this cookie to keep track of the visitors to the website. This
   cookie is passed to HubSpot on form submission and used when deduplicating
   contacts.

 * Cookie
   _hjRecordingLastActivity
 * Duration
   never
 * Description
   Hotjar sets this cookie when a user recording starts and when data is sent
   through the WebSocket.

 * Cookie
   _hjRecordingEnabled
 * Duration
   never
 * Description
   Hotjar sets this cookie when a Recording starts and is read when the
   recording module is initialized, to see if the user is already in a recording
   in a particular session.

 * Cookie
   CONSENT
 * Duration
   2 years
 * Description
   YouTube sets this cookie via embedded YouTube videos and registers anonymous
   statistical data.

 * Cookie
   vuid
 * Duration
   1 year 1 month 4 days
 * Description
   Vimeo installs this cookie to collect tracking information by setting a
   unique ID to embed videos on the website.

Performance


Performance cookies are used to understand and analyze the key performance
indexes of the website which helps in delivering a better user experience for
the visitors.

 * Cookie
   sync_active
 * Duration
   never
 * Description
   This cookie is set by Vimeo and contains data on the visitor's video-content
   preferences, so that the website remembers parameters such as preferred
   volume or video quality.

Advertisement


Advertisement cookies are used to provide visitors with customized
advertisements based on the pages you visited previously and to analyze the
effectiveness of the ad campaigns.

 * Cookie
   NID
 * Duration
   6 months
 * Description
   Google sets the cookie for advertising purposes; to limit the number of times
   the user sees an ad, to unwanted mute ads, and to measure the effectiveness
   of ads.

 * Cookie
   yt-remote-device-id
 * Duration
   never
 * Description
   YouTube sets this cookie to store the user's video preferences using embedded
   YouTube videos.

 * Cookie
   yt.innertube::requests
 * Duration
   never
 * Description
   YouTube sets this cookie to register a unique ID to store data on what videos
   from YouTube the user has seen.

 * Cookie
   yt-remote-connected-devices
 * Duration
   never
 * Description
   YouTube sets this cookie to store the user's video preferences using embedded
   YouTube videos.

 * Cookie
   yt.innertube::nextId
 * Duration
   never
 * Description
   YouTube sets this cookie to register a unique ID to store data on what videos
   from YouTube the user has seen.

 * Cookie
   YSC
 * Duration
   session
 * Description
   Youtube sets this cookie to track the views of embedded videos on Youtube
   pages.

 * Cookie
   VISITOR_INFO1_LIVE
 * Duration
   5 months 27 days
 * Description
   YouTube sets this cookie to measure bandwidth, determining whether the user
   gets the new or old player interface.

Uncategorized


Other uncategorized cookies are those that are being analyzed and have not been
classified into a category as yet.

 * Cookie
   prism_252697929
 * Duration
   1 month
 * Description
   Description is currently not available.

 * Cookie
   _hjSessionUser_2592933
 * Duration
   1 year
 * Description
   Description is currently not available.

 * Cookie
   _hjIncludedInSessionSample_2592933
 * Duration
   2 minutes
 * Description
   Description is currently not available.

 * Cookie
   _hjSession_2592933
 * Duration
   30 minutes
 * Description
   Description is currently not available.

 * Cookie
   _hjSessionUser_2063292
 * Duration
   1 year
 * Description
   Description is currently not available.

 * Cookie
   _hjIncludedInSessionSample_2063292
 * Duration
   2 minutes
 * Description
   Description is currently not available.

 * Cookie
   _hjSession_2063292
 * Duration
   30 minutes
 * Description
   Description is currently not available.

 * Cookie
   zm_aid
 * Duration
   past
 * Description
   Description is currently not available.

 * Cookie
   zm_haid
 * Duration
   past
 * Description
   Description is currently not available.

 * Cookie
   zm_tmaid
 * Duration
   past
 * Description
   Description is currently not available.

 * Cookie
   zm_htmaid
 * Duration
   past
 * Description
   Description is currently not available.

 * Cookie
   wULrMv6t
 * Duration
   session
 * Description
   Description is currently not available.

 * Cookie
   f
 * Duration
   never
 * Description
   No description available.

 * Cookie
   cred
 * Duration
   session
 * Description
   No description available.

Accept All Save My Preferences
Powered by
 * Home
 * Services
   * Overview
   * Country-code Top-level Domains (ccTLDs)
   * Generic Top-level Domains (gTLDs)
   * Brand TLDs (.brands)
 * Technology
   * Overview
   * Platform
   * DNS Services
   * Security
 * Support
   * Overview
   * Domain Whois Lookup
   * Policies
     * Overview
     * Terms and Conditions
     * Dispute Resolution
       * Overview
       * Dispute Resolution Policy
       * Supplemental Rules
       * Rules
       * Mediation Rules
       * Mediation Procedure
     * Registry Privacy Policy
     * Abuse
     * SSL Certificates
     * DNSSEC Practice Statement
     * Technology Stack Access Policy
   * Information
     * Overview
     * Supported TLDs
     * Registrars
     * RDAP
     * IDN Tables
 * About
   * Overview
   * Contact
   * News
 * Contact
 * Registrar Console


RDAP

 * Home
 * Support
 * Information
 * RDAP





RDAP AT CENTRALNIC

Last Update: March 18, 2019

INTRODUCTION

The Registration Data Access Protocol, or RDAP, replaces traditional port 43
Whois. It provides a number of enhancements relative to Whois, such as transport
security, internationalisation, a structured data format, differentiated access,
and extensibility.

RDAP builds upon HTTP and the "REST" (REpresentational State Transfer)
architectural style. RDAP servers are web servers, and RDAP clients are web
clients (which includes web browsers). RDAP responses are encoded in JSON
(JavaScript Object Notation) and are machine-readable rather than
human-readable.

RDAP was designed by the weirds working group of the Internet Engineering Task
Force (IETF), as a result of a request by ICANN for the IETF to develop a
replacement for Whois. It is now maintained by the regext working group which is
also responsible for EPP standards development.

CENTRALNIC'S RDAP SYSTEM

CentralNic's RDAP system has been implemented to comply with the following
specifications:

IETF RFCs:

 * RFC7480: HTTP Usage in the Registration Data Access Protocol (RDAP)
 * RFC7481: Security Services for the Registration Data Access Protocol (RDAP)
 * RFC7482: Registration Data Access Protocol (RDAP) Query Format
 * RFC7483: JSON Responses for the Registration Data Access Protocol (RDAP)
 * RFC7484: Finding the Authoritative Registration Data (RDAP) Service
 * RFC8056: Extensible Provisioning Protocol (EPP) and Registration Data Access
   Protocol (RDAP) Status Mapping

ICANN specifications:

 * gTLD RDAP Implementation Guide (PDF)
 * gTLD RDAP Response Profile (PDF)

CentralNic has also specified several RDAP extensions to support the gTLDs on
its platform:

 * Art Records (.ART)
 * Registration Type (.FEEDBACK)
 * Platform Nameservers (.FEEDBACK)

RDAP INFRASTRUCTURE

The RDAP system runs on the same secure, resilient, high-performance
infrastructure as the Whois system, and therefore enjoys the same reliability
and scalability. It is available over both IPv4 and IPv6.

Like the Whois, the RDAP system uses a separate replica of the primary registry
database and its own caching layer.

RATE LIMITING

The RDAP system uses the same rate-limiting system as the Whois and follows the
same policies. Note that this means that a port-43 whois counts against the RDAP
query rate, and vice versa.

SECURITY CONTROLS

RDAP is only available over HTTPS, and CentralNic's HTTPS configuration is
compliant with all current operational best practices for TLS deployment.

Additionally, a TLSA record has been published for rdap.centralnic.com, allowing
DANE-aware client applications that use DNSSEC-validating resolvers to verify
the certificate used on the RDAP service.



DEPLOYMENT PROCESS

RDAP clients which implement RFC7484 use the Bootstrap Service Registry for
Domain Name Space, operated by IANA, to determine the authoritative RDAP server
for a given domain name.

Prior to the deployment deadline of August 26th, 2019, CentralNic will add RDAP
Base URLs to each of the gTLDs for which it provides registry services. This
will allow compliant RDAP clients to automatically determine the correct RDAP
URL for domains on CentralNic's registry platform.

CentralNic also intends to deploy RDAP for all ccTLDs running on the CentralNic
platform, subject to approval by the appropriate national authorities.

Unfortunately, since the IANA can only accept registrations for top-level
domains, CentralNic's SLD portfolio cannot be added to the registry. However,
the RDAP service is available for these domains, at
https://rdap.centralnic.com/{sld}.



RDAP CLIENTS

As RDAP is a new protocol, client support is limited. However, a number of
clients exist:

 * CentralNic maintains the Net::RDAP library for the Perl programming language.
   This library is a full implementation of the complete RDAP specification. It
   can be installed from CPAN, and more information may be found at:
   
   https://gitlab.centralnic.com/centralnic/perl-net-rdap

 * rdapper is a command-line program which uses Net::RDAP to implement an
   interface similar to traditional whois clients. It can also be downloaded
   from CPAN, but more information may be found here:
   
   https://github.com/gbxyz/rdapper



USE OF RDAP FOR DOMAIN AVAILABILITY CHECKS

RDAP supports use of the HEAD HTTP method to determine the existence of a
domain.

However, the non-existence of a domain does not guarantee the availability of
that domain (since other factors, including syntactic correctness and
administrative policy) may mean that it is not available for registration.

Therefore, CentralNic does not encourage the use of RDAP HEAD queries to
determine if a domain name can be registered: the EPP <check> command should be
used instead.



STATUS OF PORT 43 WHOIS

Once RDAP has been deployed, ICANN no longer requires gTLD registries to provide
a port 43 whois service. However, in order to reduce disruption to users,
CentralNic will carry out a phased sunset plan to give users time to upgrade
their systems to use RDAP.

We will provide more information about our plans to phase out the port 43
service in due course.



COMMENTS AND QUESTIONS

If you have any comments or questions about CentralNic's RDAP system, please
email rdap@centralnic.com.

 * Home
 * Services
 * Technology
 * Support
 * About
 * News
 * Contact
 * Terms & Conditions
 * Privacy Policy
 * Site map
 * Registrar Console



Copyright © 2023  CentralNic Ltd. All Rights Reserved. CentralNic Ltd is a
subsidiary of CentralNic Group PLC.