{"id":843,"date":"2011-03-07T16:03:16","date_gmt":"2011-03-07T14:03:16","guid":{"rendered":"http:\/\/www.tld.sc\/en\/?p=843"},"modified":"2020-01-13T11:01:10","modified_gmt":"2020-01-13T09:01:10","slug":"icann-seriously-warns-jobs-registry","status":"publish","type":"post","link":"https:\/\/www.bnamed.blog\/en\/2011\/03\/icann-seriously-warns-jobs-registry\/","title":{"rendered":"ICANN seriously warns .jobs registry"},"content":{"rendered":"<p><img decoding=\"async\" loading=\"lazy\" class=\"alignright\" style=\"margin: 5px;\" src=\"http:\/\/www.goto.jobs\/images\/jobsLogo.jpg\" alt=\"\" width=\"224\" height=\"111\" \/>ICANN seriously warned Employ Media, the .jobs-registry. The reason they did this was because the .jobs registry had set up a partnership with their preferred partner the Society for Human Resource Management  (SHRM). The .jobs registry allowed this company to register domain name under the .jobs extension while these registrations weren&#8217;t in line with the current policy of the .jobs registry.<\/p>\n<p><!--more-->When ICANN, the American umbrella organisation for gTLD&#8217;s heard about this, they immediately took action. Employ media and SHRM were given 30 days in order to make sure that all .jobs names registered during this special partnership aren&#8217;t in conflict with the current .jobs policy. If this doesn&#8217;t happen ICANN will start deleting those names. Furthermore ICANN can also decide to stop their cooperation with Employ Media LLC so this company will no longer be the .jobs registry.<\/p>\n<p>Normally a .jobs domain name can only be registered by a company in order to post their own jobs on this site. Employ Media allowed SHRM to register .jobs domain names for for instance recruitment bureaus. ICANN isn&#8217;t pleased at all with this and the organisation took action.<\/p>\n<p>Below you&#8217;ll find the conditions you need to meet to register a domain name under the .jobs extension:<\/p>\n<p><span id=\"spn_outer_TLDInfo_txtRestrictiesEN_227\"><span id=\"spn_TLDInfo_txtRestrictiesEN_227\">The requested domain name under .jobs needs to resemble the company name of the company registering the domain name.<\/span><\/span><\/p>\n<p>The ability to secure a company name in .jobs is restricted to those that meet the following criteria:<\/p>\n<p>1. Tasked with hiring or other HR duties on behalf of their own employer organization;<br \/>\n2. Authorized to purchase their companyname.jobs on behalf of their employer organization;<br \/>\n3. Who agree to abide by the .jobs Use Policies published on <span id=\"spn_outer_TLDInfo_txtRestrictiesNL_227\"><span id=\"spn_TLDInfo_txtRestrictiesNL_227\">http:\/\/www.goto.jobs\/terms_of_use.asp<\/span><\/span> and<br \/>\n4. Who agree to abide by the SHRM Code of Professional Ethics published on <span id=\"spn_outer_TLDInfo_txtRestrictiesNL_227\"><span id=\"spn_TLDInfo_txtRestrictiesNL_227\">http:\/\/www.shrm.org\/about\/Pages\/code-of-ethics.aspx<\/span><\/span><\/p>\n<p>ATTENTION!  According to these rules, a .jobs-domain name may not be used to post  job openings within other companies then your own. This extension is  therefore not suitable for companies specialised in  recruitment.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>ICANN seriously warned Employ Media, the .jobs-registry. The reason they did this was because the .jobs registry had set up a partnership with their preferred partner the Society for Human Resource Management (SHRM). The .jobs registry allowed this company to register domain name under the .jobs extension while these registrations weren&#8217;t in line with the [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/843"}],"collection":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/comments?post=843"}],"version-history":[{"count":4,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/843\/revisions"}],"predecessor-version":[{"id":2138,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/843\/revisions\/2138"}],"wp:attachment":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/media?parent=843"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/categories?post=843"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/tags?post=843"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}