{"id":14031,"date":"2026-09-21T08:59:30","date_gmt":"2026-09-21T06:59:30","guid":{"rendered":"https:\/\/mybox.com\/help\/?post_type=manual_kb&#038;p=14031"},"modified":"2026-09-21T08:59:35","modified_gmt":"2026-09-21T06:59:35","slug":"explicatii-privind-infrastructura-porturilor-dns-dhcp-ntp-ldap-si-snmp","status":"publish","type":"manual_kb","link":"https:\/\/mybox.com\/help\/ro\/knowledgebase\/infrastructure-ports-explained-dns-dhcp-ntp-ldap-and-snmp\/","title":{"rendered":"Explica\u021bii privind porturile de infrastructur\u0103: DNS, DHCP, NTP, LDAP \u0219i SNMP"},"content":{"rendered":"<div class=\"translation-block translation-block-merged\">\n<p class=\"wp-block-paragraph\">Porturile de infrastructur\u0103 sus\u021bin serviciile de re\u021bea care asigur\u0103 func\u021bionarea site-urilor web, a serverelor \u0219i a re\u021belelor de afaceri. Porturile 53, 67 \u0219i 68, 123, 389 \u0219i 636, precum \u0219i 161 \u0219i 162 sunt asociate cu DNS, DHCP, NTP, LDAP \u0219i SNMP. Fiecare serviciu are un rol diferit, iar fiecare port ar trebui s\u0103 fie expus numai acolo unde este necesar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Principala distinc\u021bie se face \u00eentre TCP \u0219i UDP. TCP creeaz\u0103 o conexiune \u0219i asigur\u0103 transmiterea ordonat\u0103 a datelor. UDP trimite datagrame individuale f\u0103r\u0103 a stabili o conexiune. Combina\u021bia dintre protocol \u0219i port determin\u0103 modul \u00een care un serviciu comunic\u0103 \u0219i modul \u00een care ar trebui controlat accesul la re\u021bea.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Cuprins<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class=\"ez-toc-list ez-toc-list-level-1\"><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/infrastructure-ports-explained-dns-dhcp-ntp-ldap-and-snmp\/#Infrastructure_port_reference\">Referin\u021be privind porturile de infrastructur\u0103<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/infrastructure-ports-explained-dns-dhcp-ntp-ldap-and-snmp\/#What_port_53_does_DNS\">Ce face portul 53: DNS<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/infrastructure-ports-explained-dns-dhcp-ntp-ldap-and-snmp\/#What_ports_67_and_68_do_DHCP\">Ce fac porturile 67 \u0219i 68: DHCP<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/infrastructure-ports-explained-dns-dhcp-ntp-ldap-and-snmp\/#What_port_123_does_NTP\">Ce face portul 123: NTP<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/infrastructure-ports-explained-dns-dhcp-ntp-ldap-and-snmp\/#What_ports_389_and_636_do_LDAP_and_LDAPS\">Ce fac porturile 389 \u0219i 636: LDAP \u0219i LDAPS<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/infrastructure-ports-explained-dns-dhcp-ntp-ldap-and-snmp\/#What_ports_161_and_162_do_SNMP\">Ce fac porturile 161 \u0219i 162: SNMP<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/infrastructure-ports-explained-dns-dhcp-ntp-ldap-and-snmp\/#How_the_services_work_together\">Cum func\u021bioneaz\u0103 serviciile \u00eempreun\u0103<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cuno\u0219tin\u021be\/porturi-de-infrastructur\u0103-explicate-dns-dhcp-ntp-ldap-\u0219i-snmp\/#C\u00e2nd_ar_trebui_s\u0103_fie_deschise_porturile_de_infrastructur\u0103\">C\u00e2nd ar trebui s\u0103 fie deschise porturile de infrastructur\u0103<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Infrastructure_port_reference\"><\/span>Referin\u021b\u0103 privind porturile de infrastructur\u0103<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Port<\/th><th>Serviciu<\/th><th>Transport<\/th><th>Scop tipic<\/th><\/tr><\/thead><tbody><tr><td>53<\/td><td>DNS<\/td><td>UDP \u0219i TCP<\/td><td>Rezolv\u0103 numele de domeniu \u0219i suport\u0103 r\u0103spunsurile \u0219i transferurile DNS<\/td><\/tr><tr><td>67<\/td><td>Server DHCP<\/td><td>UDP<\/td><td>Prime\u0219te cereri de la clien\u021bii DHCP<\/td><\/tr><tr><td>68<\/td><td>Client DHCP<\/td><td>UDP<\/td><td>Prime\u0219te configura\u021bia adresei de la un server DHCP<\/td><\/tr><tr><td>123<\/td><td>NTP<\/td><td>UDP<\/td><td>Sincronizeaz\u0103 ceasurile de sistem<\/td><\/tr><tr><td>389<\/td><td>LDAP<\/td><td>TCP, \u0219i, uneori, UDP<\/td><td>Interog\u0103ri de director \u0219i comunicare prin director<\/td><\/tr><tr><td>636<\/td><td>LDAPS<\/td><td>TCP<\/td><td>Comunicare LDAP protejat\u0103 cu TLS<\/td><\/tr><tr><td>161<\/td><td>SNMP<\/td><td>UDP<\/td><td>Interog\u0103ri de monitorizare trimise c\u0103tre dispozitivele de re\u021bea<\/td><\/tr><tr><td>162<\/td><td>Trap-uri SNMP<\/td><td>UDP<\/td><td>Alerte trimise de la dispozitivele monitorizate c\u0103tre un sistem de monitorizare<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<\/div>\n\n<div id=\"mybox-4002392404\" class=\"mybox-content mybox-entity-placement\"><div class=\"early-access-banner-inpost\">\r\n  <div class=\"banner-left-inpost\">\r\n    <div class=\"icon-box-inpost\">\r\n      <img decoding=\"async\" src=\"https:\/\/mybox.com\/help\/wp-content\/uploads\/2026\/02\/square-info-icon.svg\" alt=\"Info\">\r\n    <\/div>\r\n    <div class=\"text-box-inpost\">\r\n      <span class=\"label-inpost\"><span class=\"translation-block translation-block-banner-text\">Acces timpuriu<\/span><\/span>\r\n      <h4><span class=\"translation-block translation-block-banner-text\">Mai ave\u021bi nevoie de ajutor?<\/span><\/h4>\r\n      <p><span class=\"translation-block translation-block-banner-text\">Contacta\u021bi echipa noastr\u0103 de servicii pentru clien\u021bi.<\/span><\/p>\r\n    <\/div>\r\n  <\/div>\r\n\r\n  <div class=\"banner-right-inpost\">\r\n    <a href=\"https:\/\/panel.mybox.com\/helpdesk2\/v\/list\/\" class=\"banner-button-inpost\"><span class=\"translation-block translation-block-banner-text\">Trimite mesaj<\/span><\/a>\r\n  <\/div>\r\n<\/div><\/div>\n\n<div class=\"translation-block translation-block-merged\"><p class=\"wp-block-paragraph\">Aloc\u0103rile obi\u0219nuite ale porturilor TCP \u0219i UDP sunt enumerate \u00een ghidurile de referin\u021b\u0103 privind porturile de re\u021bea, cum ar fi <a href=\"https:\/\/obelinf.com\/reference\/common-tcp-udp-ports\/?utm_source=openai\" target=\"_blank\" rel=\"noopener\">aceast\u0103 referin\u021b\u0103 privind porturile TCP \u0219i UDP<\/a> \u0219i <a href=\"https:\/\/www.internettoolset.com\/network\/port-reference?utm_source=openai\" target=\"_blank\" rel=\"noopener\">aceast\u0103 referin\u021b\u0103 privind porturile de re\u021bea<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_port_53_does_DNS\"><\/span>Ce face portul 53: DNS<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">DNS-ul traduce un nume de domeniu \u00een informa\u021bii precum adresa de destina\u021bie utilizat\u0103 pentru a accesa un serviciu. Un client trimite o interogare DNS c\u0103tre un resolver, iar acesta returneaz\u0103 un r\u0103spuns pe care clientul \u00eel poate folosi pentru a se conecta.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">DNS utilizeaz\u0103 de obicei portul UDP 53 pentru interog\u0103rile obi\u0219nuite, deoarece schimbul de date este redus \u0219i nu necesit\u0103 o conexiune persistent\u0103. Portul TCP 53 este utilizat \u0219i atunci c\u00e2nd un r\u0103spuns este prea mare pentru schimbul UDP sau c\u00e2nd sistemele DNS efectueaz\u0103 opera\u021biuni specifice de la server la server. Securitatea \u0219i disponibilitatea DNS sunt importante, deoarece problemele legate de DNS pot afecta modul \u00een care se acceseaz\u0103 serviciile. Cercet\u0103rile au examinat efectul nesiguran\u021bei DNS asupra timpului \u0219i comportamentului re\u021belei \u00een <a href=\"https:\/\/arxiv.org\/abs\/2010.09338?utm_source=openai\" target=\"_blank\" rel=\"noopener\">Impactul nesiguran\u021bei DNS asupra timpului<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Un server DNS public poate accepta \u00een mod legitim interog\u0103ri de pe internet atunci c\u00e2nd este destinat s\u0103 ofere rezolvare public\u0103 a numelor. Un resolver privat ar trebui, \u00een mod normal, s\u0103 accepte interog\u0103ri numai de la re\u021bele aprobate. Un resolver deschis poate fi utilizat \u00een mod abuziv, astfel \u00eenc\u00e2t regulile de acces ar trebui s\u0103 corespund\u0103 scopului resolverului.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_ports_67_and_68_do_DHCP\"><\/span>Ce fac porturile 67 \u0219i 68: DHCP<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">DHCP furnizeaz\u0103 clien\u021bilor set\u0103ri de re\u021bea, cum ar fi o adres\u0103 \u0219i alte configura\u021bii necesare pentru comunicare. Serverul DHCP ascult\u0103 pe portul UDP 67, \u00een timp ce clientul utilizeaz\u0103 portul UDP 68.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">DHCP este utilizat \u00een mod normal \u00een cadrul unei re\u021bele locale. Este posibil ca un client s\u0103 nu aib\u0103 \u00eenc\u0103 o adres\u0103 la pornire, astfel \u00eenc\u00e2t primul schimb de date se realizeaz\u0103 prin intermediul re\u021belei locale. Traficul DHCP este de obicei limitat la re\u021beaua \u00een care func\u021bioneaz\u0103 clien\u021bii \u0219i serverul. Routerele sau func\u021biile de retransmitere DHCP pot transmite cereri \u00eentre segmente de re\u021bea atunci c\u00e2nd arhitectura re\u021belei necesit\u0103 un server DHCP central.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Un server DHCP expus la re\u021bele ne\u00eencredere poate influen\u021ba configura\u021bia furnizat\u0103 clien\u021bilor. Securitatea DHCP a fost studiat\u0103 \u00een <a href=\"https:\/\/arxiv.org\/abs\/2502.10646?utm_source=openai\" target=\"_blank\" rel=\"noopener\">Dark Deceptions in DHCP: Dismantling Network Defenses<\/a>. Accesul public la internet prin porturile DHCP nu este o cerin\u021b\u0103 normal\u0103 pentru deservirea clien\u021bilor dintr-o re\u021bea privat\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_port_123_does_NTP\"><\/span>Ce face portul 123: NTP<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">NTP sincronizeaz\u0103 ceasurile computerelor, serverelor \u0219i dispozitivelor de re\u021bea. \u00cen mod normal, utilizeaz\u0103 portul UDP 123. Ora exact\u0103 ajut\u0103 sistemele s\u0103 \u00eenregistreze evenimentele \u00een ordinea corect\u0103 \u0219i sus\u021bine serviciile care depind de marcaje temporale consecvente.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">O organiza\u021bie poate permite solicit\u0103ri NTP de ie\u0219ire de la sistemele interne c\u0103tre o surs\u0103 de timp aprobat\u0103. Un server de timp poate accepta, de asemenea, trafic NTP de intrare de la clien\u021bi defini\u021bi. Accesul necesar depinde de faptul dac\u0103 sistemul ac\u021bioneaz\u0103 ca client, ca server de timp intern sau ca serviciu public de timp. Portul 123 nu trebuie l\u0103sat accesibil pe scar\u0103 larg\u0103 atunci c\u00e2nd serviciul nu are nevoie de clien\u021bi publici.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Ce_fac_porturile_389_\u0219i_636_LDAP_\u0219i_LDAPS\"><\/span>Ce fac porturile 389 \u0219i 636: LDAP \u0219i LDAPS<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">LDAP este un protocol pentru comunicarea cu un director. Un director poate stoca \u0219i furniza informa\u021bii utilizate de sistemele de afaceri, cum ar fi conturi, grupuri \u0219i alte intr\u0103ri din director. LDAP utilizeaz\u0103 de obicei portul TCP 389.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">LDAPS utilizeaz\u0103 portul TCP 636 \u0219i protejeaz\u0103 comunica\u021bia LDAP cu TLS. Aceasta creeaz\u0103 o diferen\u021b\u0103 important\u0103 \u00eentre cele dou\u0103 porturi: faptul c\u0103 LDAP ruleaz\u0103 pe portul 389 nu \u00eenseamn\u0103 \u00een sine c\u0103 \u00eentreaga conexiune este criptat\u0103, \u00een timp ce LDAPS este forma protejat\u0103 prin TLS. Portul 389 poate fi utilizat \u00een continuare \u00een medii care aplic\u0103 criptarea printr-o metod\u0103 negociat\u0103 separat, dar setarea de securitate trebuie s\u0103 fie deliberat\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Serviciile de director sunt, de obicei, restric\u021bionate la aplica\u021biile, serverele sau re\u021belele care au nevoie de ele. Expunerea public\u0103 poate face ca un serviciu de director s\u0103 fie accesibil sistemelor necunoscute \u0219i spore\u0219te importan\u021ba unor controale de acces puternice \u0219i a comunic\u0103rii criptate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_ports_161_and_162_do_SNMP\"><\/span>Ce fac porturile 161 \u0219i 162: SNMP<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">SNMP monitorizeaz\u0103 \u0219i gestioneaz\u0103 dispozitivele de re\u021bea. Un sistem de monitorizare trimite solicit\u0103ri c\u0103tre un dispozitiv pe portul UDP 161. Dispozitivul poate trimite o notificare nesolicitat\u0103, numit\u0103 \"trap\", c\u0103tre sistemul de monitorizare pe portul UDP 162.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Portul 161 este permis, \u00een mod normal, de la sistemele de monitorizare aprobate c\u0103tre dispozitivele gestionate. Portul 162 este permis, \u00een mod normal, de la dispozitivele gestionate c\u0103tre sistemul de monitorizare. Aceste porturi apar\u021bin, de obicei, unei re\u021bele de gestionare sau unei c\u0103i restric\u021bionate, mai degrab\u0103 dec\u00e2t internetului public. Regulile ar trebui s\u0103 separe traficul de monitorizare de traficul general al utilizatorilor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_the_services_work_together\"><\/span>Cum func\u021bioneaz\u0103 serviciile \u00eempreun\u0103<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Un client tipic utilizeaz\u0103 mai \u00eent\u00e2i DHCP pentru a primi configura\u021bia re\u021belei. Apoi utilizeaz\u0103 DNS pentru a g\u0103si adresa unui site web, a unui server sau a unui serviciu de director. Clientul poate contacta LDAP sau LDAPS pentru identitate \u0219i acces bazate pe director. NTP asigur\u0103 sincronizarea \u00eentre client \u0219i servere, \u00een timp ce SNMP permite unui sistem de monitorizare autorizat s\u0103 observe dispozitivele \u0219i s\u0103 primeasc\u0103 alerte.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Aceste servicii sunt separate, dar o problem\u0103 la unul dintre ele poate afecta celelalte. F\u0103r\u0103 DHCP, un client nou s-ar putea s\u0103 nu primeasc\u0103 set\u0103ri de re\u021bea utilizabile. F\u0103r\u0103 DNS, utilizatorii \u0219i aplica\u021biile ar putea s\u0103 nu g\u0103seasc\u0103 serviciile dup\u0103 nume. O or\u0103 de sistem incorect\u0103 poate \u00eengreuna compararea \u00eenregistr\u0103rilor de evenimente \u0219i poate afecta procesele de securitate sensibile la timp. F\u0103r\u0103 acces SNMP, un sistem de monitorizare ar putea s\u0103 nu primeasc\u0103 date despre dispozitive sau trap-uri.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"When_infrastructure_ports_should_be_open\"><\/span>C\u00e2nd ar trebui s\u0103 fie deschise porturile de infrastructur\u0103<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Deschide\u021bi un port numai pe calea de re\u021bea necesar\u0103 serviciului. Expunerea public\u0103 poate fi justificat\u0103 pentru un serviciu DNS public sau pentru un alt serviciu destinat \u00een mod inten\u021bionat publicului. Serviciile interne DHCP, de director, de timp \u0219i de monitorizare necesit\u0103, de obicei, un acces mai restr\u00e2ns, bazat pe re\u021belele client, server sau de administrare.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Permite\u021bi accesul DNS \u00een func\u021bie de faptul dac\u0103 serverul este un resolver public, un serviciu autoritar sau un resolver intern.<\/li>\n\n\n\n<li>Limita\u021bi accesul DHCP la re\u021belele care con\u021bin clien\u021bii viza\u021bi \u0219i infrastructura DHCP.<\/li>\n\n\n\n<li>Permite\u021bi NTP numai \u00eentre clien\u021bii aproba\u021bi \u0219i sursele de timp aprobate.<\/li>\n\n\n\n<li>Prefera\u021bi LDAPS sau o alt\u0103 configura\u021bie LDAP protejat\u0103 \u00een mod deliberat pentru comunicarea de director care traverseaz\u0103 o re\u021bea ne\u00eencredibil\u0103.<\/li>\n\n\n\n<li>Permite\u021bi solicit\u0103rile \u0219i trap-urile SNMP numai \u00eentre dispozitivele gestionate \u0219i sistemele de monitorizare aprobate.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Serviciile expuse c\u0103tre Internet ar trebui revizuite ca parte a proiectului general de securitate. Vulnerabilit\u0103\u021bile serviciilor deschise pot expune sistemele atunci c\u00e2nd un serviciu este accesibil f\u0103r\u0103 controalele corespunz\u0103toare rolului s\u0103u, a\u0219a cum este descris \u00een <a href=\"https:\/\/www.rogers.com\/support\/internet\/open-service-vulnerabilities?utm_source=openai\" target=\"_blank\" rel=\"\u2019noopener&quot;\">prezentarea general\u0103 a lui Rogers privind vulnerabilit\u0103\u021bile serviciilor deschise<\/a>. Configura\u021bia corect\u0103 nu const\u0103 \u00een deschiderea tuturor porturilor standard, ci \u00een permiterea traficului exact necesar fiec\u0103rui serviciu de infrastructur\u0103.<\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"template":"","format":"standard","manualknowledgebasecat":[25],"manual_kb_tag":[],"class_list":["post-14031","manual_kb","type-manual_kb","status-publish","format-standard","hentry","manualknowledgebasecat-hosting"],"_links":{"self":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/14031","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/14031\/revisions"}],"predecessor-version":[{"id":14032,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/14031\/revisions\/14032"}],"wp:attachment":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/media?parent=14031"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manualknowledgebasecat?post=14031"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb_tag?post=14031"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}