{"id":6399,"date":"2019-12-11T11:01:23","date_gmt":"2019-12-11T11:01:23","guid":{"rendered":"https:\/\/www.icdsoft.com\/blog\/?p=6399"},"modified":"2026-03-19T08:15:09","modified_gmt":"2026-03-19T08:15:09","slug":"the-battle-for-the-amazon","status":"publish","type":"post","link":"https:\/\/www.icdsoft.com\/blog\/the-battle-for-the-amazon\/","title":{"rendered":"The Battle for the .amazon"},"content":{"rendered":"\n<p>Two powerful parties fought a fierce battle that lasted more than seven years, and (kind of) ended a few months ago. The future of the <em>.amazon<\/em> was at stake. You read that right \u2013 the dispute was over the right to manage the <em>.amazon<\/em> top-level domain. The parties involved were Amazon Inc. on one side, and the countries from the Amazon basin on the other, with Brazil and Peru being most active. Hundreds of new TLDs have been introduced in the last several years, but we are still looking forward to the launch of <em>.amazon<\/em> due to the clash between national governments, and one of the largest corporations in the world. In this article, we will have a look at how the events unfolded, and who won this battle. This interesting case shows that sometimes online matters may cross borders, and go way beyond the online world.<\/p>\n\n\n\n<div style=\"color:#32373c;background-color:#3373dc\" class=\"wp-block-genesis-blocks-gb-notice gb-font-size-18 gb-block-notice\" data-id=\"7299ec\"><div class=\"gb-notice-title\" style=\"color:#fff\"><p>The key players<\/p><\/div><div class=\"gb-notice-text\" style=\"border-color:#3373dc\"><p>- ICANN - the Internet Corporation for Assigned Names and Numbers is a nonprofit organization that manages the domain name system. It is seen as the Internet overlord as it adopts and enforces policies how domains should work, what domain extensions should exist, and who should manage them.<\/p><p>- GAC - Governmental Advisory Committee. A group within ICANN that represents governments and intergovernmental organizations. Currently consists of 178 members and 38 observers. GAC provides public policy advice on matters that are related to national and international laws and agreements.<\/p><p>- ACTO - Amazon Cooperation Treaty Organization. Its member states are Bolivia, Brazil, Colombia, Ecuador, Guyana, Peru, Suriname and Venezuela. The organization aims at promoting sustainable development of the Amazon Basin. It is seated in Brasilia, Brazil.<\/p><p>- Amazon - A multinational corporation, which is focused on e-commerce, cloud hosting and computing, content streaming, and technology. It is the 13th largest company in Fortune500 with $232 bln. revenue (2018). <\/p><\/div><\/div>\n\n\n\n<h4 class=\"wp-block-heading\">ICANN\u2019s New gTLD Program<\/h4>\n\n\n\n<p>In 2011, ICANN\u2019s Board of Directors voted in favor of a change that would affect dramatically the Internet as we knew it. They decided to introduce hundreds of new domain extensions in addition to the 22 generic TLDs that had existed up until then. The New gTLD Program was an initiative to enhance competition, and to give customers a choice, as most good names with the original TLDs had already been taken.<\/p>\n\n\n\n<p>The application process started in 2012, and companies got the green light to submit their proposals for new extensions to ICANN for consideration. These included generic TLDs such as <em>.shop<\/em>, <em>.ninja<\/em>, <em>.xyz<\/em>, or <em>.website<\/em>, as well as company-specific ones such as <em>.google<\/em>, <em>.aws<\/em>, or <em>.bmw<\/em>. The latter became known as branded TLDs, and they represented about 34% of all applications for new TLDs. While there was no formal difference between these two types of TLDs, the branded ones were not intended to be open for public use. Any company that would start operating a brand TLD registry would have the exclusive right to use the TLD solely for its own websites, products, and services.<\/p>\n\n\n\n<script type=\"text\/javascript\" src=\"https:\/\/www.gstatic.com\/charts\/loader.js\"><\/script>\n<div id=\"piechart\" style=\"width: 900px; height: 500px;\"><\/div>\n<script>\n      google.charts.load('current', {\n        'packages': ['corechart']\n      });\n      google.charts.setOnLoadCallback(drawChart);\n\n      function drawChart() {\n\n        var data = google.visualization.arrayToDataTable([\n          ['Type', 'Number'],\n          ['Other gTLD applications', 1280],\n          ['Branded TLD applications (active as of Dec 2019)', 178],\n          ['Branded TLD applications (still pending as of Dec 2019)', 472],\n\n        ]);\n\n        var options = {\n          title: '1930 gTLD applications were submitted in 2012, 650 of them for branded TLDs.'\n        };\n\n        var chart = new google.visualization.PieChart(document.getElementById('piechart'));\n\n        chart.draw(data, options);\n      }\n<\/script>\n\n\n\n<p>One of the companies that submitted an application for a number of new TLDs was Amazon Registry Services. Currently, they operate Amazon\u2019s portfolio of 52 TLDs, including service-related ones like <em>.aws<\/em>, <em>.kindle<\/em>, <em>.prime<\/em>, <em>.imdb<\/em>, as well as the more generic <em>.book<\/em>, <em>.bot<\/em>, <em>.free<\/em>, <em>.pay<\/em>, etc. The absence of one extension from this list stands out a mile - <em>.amazon<\/em>. The reason is that the countries from the Amazon basin strongly opposed the delegation of this TLD to a private company.<\/p>\n\n\n\n<div style=\"color:#32373c;background-color:#3373dc\" class=\"wp-block-genesis-blocks-gb-notice gb-font-size-18 gb-block-notice\" data-id=\"76e0df\"><div class=\"gb-notice-title\" style=\"color:#fff\"><p>Why a Branded TLD?<\/p><\/div><div class=\"gb-notice-text\" style=\"border-color:#3373dc\"><p>A few key advantages of using a branded extension are brand recognition,  trademark security, and better control over branded second-level domains.<\/p><\/div><\/div>\n\n\n\n<h4 class=\"wp-block-heading\">The Amazon vs. Amazon<\/h4>\n\n\n\n<p>Amazon Inc. submitted their application for the <em>.amazon<\/em> TLD in 2012. They passed the ICANN assessments with a perfect score - 41 out of 41 points. In July 2013, ICANN held a meeting in Durban, South Africa, to review the applications for the new wave of extensions. It was expected that many TLDs would be approved, <em>.amazon<\/em> being among them. Surprisingly, a number of countries from the Amazon basin sent a letter to the Governmental Advisory Committee of ICANN (GAC) just before the meeting. GAC is the group that represents governments within ICANN. The letter stated that<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>'<em>.amazon<\/em>\u2019 is a geographic name that represents important territories of some of our countries, which have relevant communities, with their own culture and identity directly connected with the name. Beyond the specifics, this should also be understood as a matter of principle\u201d. <\/p><\/blockquote>\n\n\n\n<p>As a result, <a rel=\"noreferrer noopener\" aria-label=\"GAC recommended (opens in a new tab)\" href=\"https:\/\/www.icann.org\/resources\/board-material\/resolutions-new-gtld-2014-05-14-en#2.b\" target=\"_blank\">GAC recommended<\/a> that ICANN rejects Amazon\u2019s application. For more than a year after Amazon had applied for the new extension  there had been no indication that any party would object. In this light, it was a surprise that a coalition of countries did that, and in such an aggressive manner. Brazil and Peru expressed the strongest opinion against the possible delegation of the TLD to the US-based corporation. Some people speculated that there was a connection between the objection, and the information disclosed by Edward Snowden just a couple of weeks earlier. The documents he leaked revealed that the NSA had tapped the phone of the Brazilian president Dilma Rousseff. It is believed that going against Amazon was a part of Brazil\u2019s forceful response to the leaks. Whatever the reason, the result was that ICANN formally put the delegation of the <em>.amazon<\/em> domain on hold in 2014. <\/p>\n\n\n\n<p>In turn, Amazon appealed, and in 2016 asked an independent panel to review ICANN\u2019s decision. The panel found that ICANN had not justified its rejection, and had not allowed Amazon to present its case. It ordered the organization to reassess its decision. ICANN, however, decided to stay away from the controversy, and told the two sides to settle the dispute among themselves.  <\/p>\n\n\n\n<p>There was no progress for a couple of years, as neither side would take a step back. Brazil, backed by the rest of the countries in ACTO (Amazon Cooperation Treaty Organization) kept on insisting that <em>.amazon<\/em> should be used solely by state actors as to preserve their cultural heritage, and to prevent a corporation from using it to make money. Amazon repeatedly wrote to ICANN, saying that there was no policy or any \u201csovereign right under national or international law to the name Amazon\u201d, so there was no viable reason for its application to be rejected. The company also contacted the Brazilian government directly in an attempt to persuade them to stop their opposition to the new TLD, but to no avail.<\/p>\n\n\n\n<div style=\"color:#32373c;background-color:#3373dc\" class=\"wp-block-genesis-blocks-gb-notice gb-font-size-15 gb-block-notice\" data-id=\"477fda\"><div class=\"gb-notice-title\" style=\"color:#fff\"><p>What Amazon offered the ACTO countries<\/p><\/div><div class=\"gb-notice-text\" style=\"border-color:#3373dc\"><p>- Kindle e-readers and AWS hosting services for up to $5 mln.\u00a0<\/p><p>- To promote Amazonian culture (est. budget\u00a0 $1 mln over four years)\u00a0<\/p><p>- To support ACTO in getting a new <em>.amazonia<\/em> TLD\u00a0<\/p><p>- To block the registration of any <em>.amazon<\/em> name from a list of 1500 protected words\u00a0<\/p><p>- To give ACTO nine domains for exclusive use, one for each country (<em>.br.amazon<\/em>, for example)\u00a0<\/p><\/div><\/div>\n\n\n\n<p>ICANN inquired about progress a couple of times, but would still not proceed with either approving Amazon\u2019s application, or putting it on permanent hold. Industry watchers questioned the organization\u2019s independence and decisiveness, as it was allowing governments to meddle into its matters. A new gTLD would normally take two years to be launched. Google, for example, applied for a new extension in 2012 as well, and launched <em>.google<\/em> in 2014. <\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"alignright size-large is-resized\"><img decoding=\"async\" data-src=\"https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/marby-678x1024.jpg\" alt=\"Man in suit speaking at a podium during an event with plants in the background and university emblem visible.\" class=\"wp-image-6430 lazyload\" width=\"214\" height=\"323\" data-srcset=\"https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/marby-678x1024.jpg 678w, https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/marby-199x300.jpg 199w, https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/marby-768x1160.jpg 768w, https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/marby-1017x1536.jpg 1017w, https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/marby.jpg 1024w\" data-sizes=\"(max-width: 214px) 100vw, 214px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 214px; --smush-placeholder-aspect-ratio: 214\/323;\" \/><figcaption>G\u00f6ran Marby<\/figcaption><\/figure><\/div>\n\n\n\n<p>In 2018, ICANN appointed its own CEO G\u00f6ran Marby to host meetings between the two parties until an agreement was reached. His attempts turned out to be a big failure, as the ACTO countries, and Brazil in particular, were unwilling to negotiate. They kept insisting on having full control over the <em>.amazon<\/em> TLD. A vivid example of their reluctance was Marby\u2019s trip to Sao Paulo at the end of 2018, when a meeting was cancelled by Brazil in the very last moment, and no talks took place at all. As an excuse, the local government pointed out that representatives from Venezuela would not be present due to the civil unrest in the country. They ignored the fact that all other countries were represented, and that Marby was already in the country for the meeting. Several more attempts to facilitate discussions with the ACTO countries failed in the following months.<\/p>\n\n\n\n<p>Marby\u2019s failed efforts attracted heavy criticism from the industry and from the ACTO governments, and this failure was a turning point. ICANN\u2019s Board of Directors finally got fed up with the lack of progress, as the organization\u2019s reputation was at stake. They decided to take matters in their own hands. In May 2019, <a rel=\"noreferrer noopener\" aria-label=\"the Board finally accepted (opens in a new tab)\" href=\"https:\/\/www.icann.org\/resources\/board-material\/resolutions-2019-05-15-en#1.c\" target=\"_blank\">the Board finally accepted<\/a> Amazon\u2019s latest proposal, and asked the organization CEO to proceed with their application for <em>.amazon<\/em>.<\/p>\n\n\n\n<p class=\"has-small-font-size\"><strong>Similar cases<\/strong><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"alignright size-large\"><img decoding=\"async\" width=\"234\" height=\"118\" data-src=\"https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/dotbar-2.png\" alt=\".bar domain logo with cocktail glass, wine bottle, and beer mug icons in purple color theme.\" class=\"wp-image-6414 lazyload\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 234px; --smush-placeholder-aspect-ratio: 234\/118;\" \/><\/figure><\/div>\n\n\n\n<p class=\"has-small-font-size\">The clothing company Patagonia had applied for <em>.patagonia<\/em>  in 2012, but withdrew its application before the ICANN meeting in  Durban in 2013 under pressure from Argentina. Patagonia is the name of a  large region shared between Argentina and Chile.&nbsp;<\/p>\n\n\n\n<p class=\"has-small-font-size\">In 2014, <em>.bar<\/em> was launched after a Mexican registry company reached an agreement with the Montenegrin city of Bar over the exclusive rights to use the TLD.&nbsp;<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Amazon won the battle\u2026<\/h4>\n\n\n\n<p>Although the dispute seemed to be over, a final decision had not been reached. ICANN decided to wait until September 2019 to publish Amazon\u2019s public commitments regarding the TLD, and to allow some time for comments from interested parties. This move seemed like taking a step back, and it was no surprise that Brazil officially objected through GAC in October 2019, saying that giving <em>.amazon<\/em> to a corporation was an \u201cexpropriation from the Amazon countries\u201d, and that the word \u201cAmazon\u201d was its \u201cbirthright\u201d. This time, however, after not taking sides for seven years, the US representative in GAC sharply opposed any further delays or discussions. China, Portugal, Switzerland and the European Commission asked for more negotiations, while Israel supported the US. We will have to wait and see if ICANN will overcome the objections of some governments, and if it will take a decision on Amazon\u2019s application once and for all. This is expected to happen in the next several months, and for the time being, industry watchers expect a positive outcome for Amazon Inc. <\/p>\n\n\n\n<h4 class=\"wp-block-heading\">\u2026 but everybody lost the war. <\/h4>\n\n\n\n<p>Although we may be looking at the resolution of this dispute, none of the parties can claim a real victory. On the contrary, they all lost to some extent.  <\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"alignright size-large is-resized\"><img decoding=\"async\" data-src=\"https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazonlogo-1024x683.jpg\" alt=\"Exterior of Amazon pickup and returns building with modern signage against a blue sky background.\" class=\"wp-image-6433 lazyload\" width=\"251\" height=\"166\" data-srcset=\"https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazonlogo-1024x683.jpg 1024w, https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazonlogo-300x200.jpg 300w, https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazonlogo-768x512.jpg 768w, https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazonlogo-1536x1024.jpg 1536w, https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazonlogo-600x400.jpg 600w, https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazonlogo-270x180.jpg 270w, https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazonlogo-370x245.jpg 370w\" data-sizes=\"(max-width: 251px) 100vw, 251px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 251px; --smush-placeholder-aspect-ratio: 251\/166;\" \/><figcaption>There is no return for Amazon<\/figcaption><\/figure><\/div>\n\n\n\n<p>Amazon lost more than seven years in legal battles, trying to get a branded top-level domain, wasting money and effort. It already runs extensions that match its services, like <em>.aws<\/em> and <em>.kindle<\/em>. The <em>.amazon<\/em> one, however, now stands for more than just a name. The dispute has turned it into a symbol of the clash between governments on one side, and the Internet authority and the private sector on the other. Amazon has already invested too much, and cannot afford to walk out on the TLD, so it will keep on fighting to the end. <\/p>\n\n\n\n<p>ICANN lost some of the trust it had as a governing body. It ignored its own bylaws, and rejected a total of five applications from Amazon over a period of seven years with no explanation whatsoever. It failed to take a definitive decision, and asked the two parties in the dispute to reach an agreement among themselves, thus forsaking its role of an Internet authority that has the final say. As a result of the ongoing feud, registry organizations, registrars, and other domain organizations have lost some of their confidence in ICANN, which may have a long-term negative effect for new and old TLDs. You can also check out <a rel=\"noreferrer noopener\" aria-label=\"our article about the ongoing .ORG controversy (opens in a new tab)\" href=\"https:\/\/www.icdsoft.com\/blog\/the-org-controversy\/\" target=\"_blank\">our article about the ongoing .ORG controversy<\/a>, which already has a negative impact on all parties involved, including ICANN. <\/p>\n\n\n\n<p>Brazil lost its reputation as a trustworthy partner in this dispute. Their constant objections to Amazon\u2019s TLD applications and resolution proposals indicated that the Brazilian government most probably had some hidden agenda. While there might have been ground for their initial objection, their stubbornness turned out to be counterproductive. Sending letters to ICANN with the same arguments against the TLD delegation over and over again resulted in the community not taking them seriously anymore. <\/p>\n\n\n\n<p>The United States did not get involved in this dispute until November 2019, when they took a side for the first time in seven years. Staying aloof  was not necessarily a good thing though. Many observers believe that this behavior showed that they may have lost their role as a global leader and an informal regulator in the online world. <\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Conclusion<\/h4>\n\n\n\n<p>The dispute over the <em>.amazon <\/em>top-level domain shows how international politics and Internet policy can get mixed up, and how a national government can affect the business of a private company, even if the two have nothing in common. The outcome may have serious repercussions for the online world if ICANN does not stand by its own bylaws, and if it submits to government pressure. This may create a dangerous precedent. As a side effect of the dispute, it is likely that many companies that wanted to register a branded TLD, have changed their minds after seeing ICANN\u2019s lack of determination, and their dependence on state actors. The seven-year long application process, and the lack of flexibility and compromise from one of the sides turned an otherwise trivial process into a virtual war. One that is not in anybody\u2019s interest, and that already has a great impact on the TLD world.<\/p>\n\n\n\n<p>To check out all active branded TLDs, go to\u00a0<a rel=\"noreferrer noopener\" href=\"https:\/\/www.brandtld.news\/brand-tld-use-cases\/\" target=\"_blank\">https:\/\/www.brandtld.news\/brand-tld-use-cases\/<\/a><\/p>\n\n\n\n<hr class=\"wp-block-separator\"\/>\n\n\n\n<p>ICDSoft is a hosting company operating since 2001. We offer domain name registrations at fair prices. Check <a rel=\"noreferrer noopener\" aria-label=\"https:\/\/www.icdsoft.com\/en\/domains (opens in a new tab)\" href=\"https:\/\/www.icdsoft.com\/en\/domains\" target=\"_blank\">https:\/\/www.icdsoft.com\/en\/domains<\/a> for more details. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Two powerful parties fought a fierce battle that lasted for more than seven years, and (kind of) ended a few months ago. The future of the .amazon was at stake.<\/p>\n","protected":false},"author":1,"featured_media":6419,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"advgb_blocks_editor_width":"","advgb_blocks_columns_visual_guide":"","footnotes":""},"categories":[1,24],"tags":[],"class_list":{"0":"post-6399","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-general","8":"category-domains"},"author_meta":{"display_name":"ICDSoft","author_link":"https:\/\/www.icdsoft.com\/blog\/author\/icdsoft\/"},"featured_img":"https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazon-300x169.jpg","featured_image_src":"https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazon.jpg","featured_image_src_square":"https:\/\/www.icdsoft.com\/blog\/wp-content\/uploads\/2019\/12\/amazon.jpg","author_info":{"display_name":"ICDSoft","author_link":"https:\/\/www.icdsoft.com\/blog\/author\/icdsoft\/"},"coauthors":[],"tax_additional":{"categories":{"linked":["<a href=\"https:\/\/www.icdsoft.com\/blog\/category\/general\/\" class=\"advgb-post-tax-term\">General<\/a>","<a href=\"https:\/\/www.icdsoft.com\/blog\/category\/domains\/\" class=\"advgb-post-tax-term\">Domains<\/a>"],"unlinked":["<span class=\"advgb-post-tax-term\">General<\/span>","<span class=\"advgb-post-tax-term\">Domains<\/span>"]}},"comment_count":"0","relative_dates":{"created":"Posted 7 years ago","modified":"Updated 5 months ago"},"absolute_dates":{"created":"Posted on December 11, 2019","modified":"Updated on March 19, 2026"},"absolute_dates_time":{"created":"Posted on December 11, 2019 11:01 am","modified":"Updated on March 19, 2026 8:15 am"},"featured_img_caption":"","series_order":"","_links":{"self":[{"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/posts\/6399","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/comments?post=6399"}],"version-history":[{"count":36,"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/posts\/6399\/revisions"}],"predecessor-version":[{"id":14934,"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/posts\/6399\/revisions\/14934"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/media\/6419"}],"wp:attachment":[{"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/media?parent=6399"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/categories?post=6399"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.icdsoft.com\/blog\/wp-json\/wp\/v2\/tags?post=6399"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}