{"id":192,"date":"2026-02-13T09:26:56","date_gmt":"2026-02-13T08:26:56","guid":{"rendered":"https:\/\/helloblog.io\/sk\/smtp-porty-v-roku-2026-ako-vybrat-spravny-port-pre-wordpress-email\/"},"modified":"2026-02-13T09:26:56","modified_gmt":"2026-02-13T08:26:56","slug":"smtp-porty-v-roku-2026-ako-vybrat-spravny-port-pre-wordpress-email","status":"publish","type":"post","link":"https:\/\/helloblog.io\/sk\/smtp-porty-v-roku-2026-ako-vybrat-spravny-port-pre-wordpress-email\/","title":{"rendered":"SMTP porty v roku 2026: ako vybra\u0165 spr\u00e1vny port, aby WordPress e-maily nekon\u010dili v spame"},"content":{"rendered":"\n<p>Ak prev\u00e1dzkuje\u0161 web, berie\u0161 ako samozrejmos\u0165, \u017ee e-maily bud\u00fa fungova\u0165: spr\u00e1vy z kontaktn\u00e9ho formul\u00e1ra pr\u00eddu do inboxu, z\u00e1kazn\u00edk dostane potvrdenie objedn\u00e1vky a reset hesla doraz\u00ed okam\u017eite. Ke\u010f sa to nedeje, nie je to len nepr\u00edjemnos\u0165. Je to naru\u0161enie d\u00f4very, ktor\u00e9 stoj\u00ed leady, z\u00e1kazn\u00edkov aj reput\u00e1ciu.<\/p>\n\n\n\n<p>V praxi je \u201etich\u00fdm vinn\u00edkom\u201c naj\u010dastej\u0161ie defaultn\u00e9 odosielanie po\u0161ty z webu. Mnoho webov (najm\u00e4 WordPress) posiela e-maily sp\u00f4sobom, ktor\u00fd z poh\u013eadu Gmailu \u010di Outlooku vyzer\u00e1 podozrivo \u2013 ve\u013emi podobne ako spam.<\/p>\n\n\n\n<p>Rie\u0161enie je ob\u00eds\u0165 nespo\u013eahliv\u00fd default a posiela\u0165 e-maily cez profesion\u00e1lny, autentifikovan\u00fd kan\u00e1l pomocou SMTP (Simple Mail Transfer Protocol). Len\u017ee pri nastavovan\u00ed naraz\u00ed\u0161 na jednu zdanlivo jednoduch\u00fa, ale kritick\u00fa ot\u00e1zku: ktor\u00fd SMTP port je spr\u00e1vna vo\u013eba v roku 2026?<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Najd\u00f4le\u017eitej\u0161ie zhrnutie (\u010do si zapam\u00e4ta\u0165)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>R\u00fdchla odpove\u010f: pou\u017e\u00edvaj <strong>port 587<\/strong> so \u0161ifrovan\u00edm <strong>STARTTLS<\/strong>. Je to modern\u00fd, bezpe\u010dn\u00fd a odpor\u00fa\u010dan\u00fd \u0161tandard na odosielanie e-mailov z webu alebo klienta.<\/li>\n\n\n<li>Dobr\u00e1 alternat\u00edva: <strong>port 465<\/strong> so <strong>SMTPS<\/strong> (implicitn\u00e9 SSL\/TLS). Je tie\u017e ve\u013emi be\u017en\u00fd a bezpe\u010dn\u00fd; niektor\u00ed poskytovatelia ho dokonca preferuj\u00fa. Ke\u010f 587 nefunguje, 465 je \u010fal\u0161ia najlep\u0161ia vo\u013eba.<\/li>\n\n\n<li>Port, ktor\u00e9mu sa vyhni: <strong>nikdy nepou\u017e\u00edvaj port 25<\/strong> na e-mail <em>submission<\/em> (t. j. odosielanie z webu). Je ne\u0161ifrovan\u00fd, ur\u010den\u00fd na server-to-server relaying a modern\u00ed provideri\/hostingy ho \u010dasto blokuj\u00fa kv\u00f4li spamu.<\/li>\n\n\n<li>Skuto\u010dn\u00fd probl\u00e9m (pre\u010do to pad\u00e1): defaultn\u00e1 funkcia webu (v WordPress napr. <code>wp_mail()<\/code>) je <strong>neautentifikovan\u00e1<\/strong>. Odo\u0161le po\u0161tu z webservera bez e-mailovej reput\u00e1cie, \u010do spam filtre vyhodnocuj\u00fa ako riziko.<\/li>\n\n\n<li>Skuto\u010dn\u00e9 rie\u0161enie (ako to opravi\u0165): pou\u017e\u00edvaj <strong>dedikovan\u00fa SMTP slu\u017ebu<\/strong> (napr. SendGrid, Brevo, Mailgun), ktor\u00e1 po\u0161tu posiela cez d\u00f4veryhodn\u00fd a autentifikovan\u00fd server.<\/li>\n\n\n<li>\u201eEasy button\u201c pre WordPress: plugin bez komplikovanej konfigur\u00e1cie, napr. <a href=\"https:\/\/elementor.com\/products\/site-mailer\">Site Mailer by Elementor<\/a>, vie presmerova\u0165 transak\u010dn\u00e9 e-maily bez toho, aby si rie\u0161il porty, DNS alebo API k\u013e\u00fa\u010de.<\/li>\n\n\n<li>Transak\u010dn\u00e9 vs. marketingov\u00e9 e-maily: SMTP slu\u017eba je na <strong>transak\u010dn\u00e9 e-maily<\/strong> (formul\u00e1re, resety, \u00fa\u010dtenky). Newslettery a hromadn\u00e9 kampane posielaj cez samostatn\u00fa <strong>email marketing platformu<\/strong> (ESP), aby si si nezni\u010dil reput\u00e1ciu odosielania.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">\u010co je SMTP a pre\u010do je to pre web kritick\u00e9<\/h2>\n\n\n\n<p>SMTP (Simple Mail Transfer Protocol) si predstav ako ofici\u00e1lnu digit\u00e1lnu po\u0161tu internetu. Je to univerz\u00e1lny \u201epravidlov\u00fd zo\u0161it\u201c, pod\u013ea ktor\u00e9ho e-mailov\u00e9 klienty (Outlook, Apple Mail) a e-mailov\u00e9 servery posielaj\u00fa a preberaj\u00fa spr\u00e1vy.<\/p>\n\n\n\n<p>Ke\u010f odo\u0161le\u0161 e-mail, nelet\u00ed priamo pr\u00edjemcovi. Typicky sa dej\u00fa tri kroky:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>E-mail sa odo\u0161le na tvoj <strong>odch\u00e1dzaj\u00faci mail server<\/strong> (napr. <code>smtp.gmail.com<\/code>). Toto je krok <em>submission<\/em> (odovzdanie spr\u00e1vy na odoslanie).<\/li>\n\n\n<li>Tvoj mail server potom n\u00e1jde server pr\u00edjemcu a spr\u00e1vu mu <strong>relayne<\/strong> (prepo\u0161le).<\/li>\n\n\n<li>Server pr\u00edjemcu e-mail ulo\u017e\u00ed a \u010dak\u00e1, k\u00fdm si pr\u00edjemca otvor\u00ed inbox.<\/li>\n\n<\/ol>\n\n\n\n<p>SMTP sa t\u00fdka kroku #1 (submission) aj #2 (relay). A \u201eSMTP port\u201c je jednoducho konkr\u00e9tne \u010d\u00edslovan\u00e9 \u201edvere\u201c na serveri, cez ktor\u00e9 sa tento proces realizuje.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Probl\u00e9m WordPressu: <code>wp_mail()<\/code><\/h3>\n\n\n\n<p>WordPress v z\u00e1klade \u010dasto nepou\u017e\u00edva SMTP. Namiesto toho posiela e-mail cez PHP funkciu <code>wp_mail()<\/code>, ktor\u00e1 sa pok\u00fasi odosla\u0165 spr\u00e1vu priamo z webservera.<\/p>\n\n\n\n<p>Z poh\u013eadu doru\u010dite\u013enosti je to ve\u013ek\u00fd probl\u00e9m:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li><strong>Webserver nie je mail server:<\/strong> je optimalizovan\u00fd na obsluhu webu, nie na odosielanie po\u0161ty. Ch\u00fdba mu \u201epo\u0161tov\u00e1\u201c v\u00fdbava a spr\u00e1vne konfigur\u00e1cie.<\/li>\n\n\n<li><strong>Ch\u00fdba autentifik\u00e1cia:<\/strong> server len tvrd\u00ed, \u017ee posiela po\u0161tu z tvojej dom\u00e9ny (napr. <code>tvoja-domena.sk<\/code>), ale nem\u00e1 siln\u00e9 d\u00f4kazy, \u017ee na to m\u00e1 opr\u00e1vnenie.<\/li>\n\n\n<li><strong>\u017diadna reput\u00e1cia odosielate\u013ea:<\/strong> Gmail\/Microsoft maj\u00fa reputa\u010dn\u00e9 sk\u00f3re pre zn\u00e1me mail servery. Webserver typicky nem\u00e1 e-mailov\u00fa reput\u00e1ciu, tak\u017ee p\u00f4sob\u00ed ako nov\u00fd nezn\u00e1my odosielate\u013e.<\/li>\n\n\n<li><strong>Zl\u00e1 IP \u201e\u0161tvr\u0165\u201c na zdie\u013eanom hostingu:<\/strong> na shared hostingu m\u00f4\u017ee by\u0165 na jednej IP stovky webov. Ak niektor\u00fd z nich spamuje, IP sa m\u00f4\u017ee dosta\u0165 na blacklist a trpia aj legit\u00edmne weby.<\/li>\n\n<\/ol>\n\n\n\n<p>V\u00fdsledok je predv\u00eddate\u013en\u00fd: inbox provideri uvidia neautentifikovan\u00fd e-mail bez reput\u00e1cie z \u201ewebservera\u201c, a skon\u010d\u00ed v spame \u2013 alebo bude potichu zablokovan\u00fd.<\/p>\n\n\n\n<p>Rie\u0161en\u00edm je don\u00fati\u0165 WordPress (alebo in\u00fd web) nepou\u017e\u00edva\u0165 defaultn\u00e9 odosielanie, ale posiela\u0165 cez profesion\u00e1lne SMTP\/transactional e-mail slu\u017eby. A pri tom prich\u00e1dza na sc\u00e9nu spr\u00e1vny port.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kr\u00e1tka hist\u00f3ria SMTP portov (a pre\u010do s\u00fa niektor\u00e9 dnes prakticky m\u0155tve)<\/h2>\n\n\n\n<p>Ak chce\u0161 rozumie\u0165, pre\u010do je dnes odpor\u00fa\u010dan\u00fd pr\u00e1ve jeden port, pom\u00f4\u017ee vedie\u0165, pre\u010do existuj\u00fa tie ostatn\u00e9. Hist\u00f3ria SMTP portov je v z\u00e1sade hist\u00f3ria boja internetu proti spamu.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Port 25: p\u00f4vodn\u00fd \u201espamov\u00fd dia\u013eni\u010dn\u00fd \u0165ah\u201c<\/h3>\n\n\n\n<p>Na za\u010diatku (v roku 1982) tu bol prakticky len <strong>port 25<\/strong>. Bol navrhnut\u00fd pre relaying e-mailov medzi mail servermi (Mail Transfer Agents \u2013 MTA). Bol otvoren\u00fd, jednoduch\u00fd a bez autentifik\u00e1cie: ktor\u00fdko\u013evek server sa mohol pripoji\u0165 na port 25 in\u00e9ho servera a odovzda\u0165 mu e-mail.<\/p>\n\n\n\n<p>V akademickom, d\u00f4veruj\u00facom internete to fungovalo. K\u00fdm nepri\u0161li spameri.<\/p>\n\n\n\n<p>Probl\u00e9m bol jasn\u00fd: spamer mohol cez port 25 nak\u0155mi\u0165 cudz\u00ed server obrovsk\u00fdm mno\u017estvom nevy\u017eiadanej po\u0161ty a necha\u0165 ho doru\u010dova\u0165 spr\u00e1vy \u201eza seba\u201c. Ne\u0161ifrovan\u00e1, neautentifikovan\u00e1 dia\u013enica pre zneu\u017eitie.<\/p>\n\n\n\n<p>Dnes preto takmer ka\u017ed\u00fd ISP, cloud provider aj be\u017en\u00e9 reziden\u010dn\u00e9 siete <strong>blokuj\u00fa odch\u00e1dzaj\u00face spojenia na port 25<\/strong>. Robia to, aby zastavili spam boty na zav\u00edren\u00fdch po\u010d\u00edta\u010doch a kompromitovan\u00fdch serveroch.<\/p>\n\n\n\n<div class=\"wp-block-group callout callout-warning is-style-warning is-layout-flow wp-block-group-is-layout-flow\" style=\"border-width:1px;border-radius:8px;padding-top:1rem;padding-right:1.5rem;padding-bottom:1rem;padding-left:1.5rem\">\n\n<h4 class=\"wp-block-heading callout-title\">D\u00f4le\u017eit\u00e9<\/h4>\n\n\n<p>Port 25 nepou\u017e\u00edvaj na e-mail submission z webu. Aj keby to hosting umo\u017enil (nemal by), zvy\u0161ok internetu to \u010dasto zablokuje.<\/p>\n\n<\/div>\n\n\n\n<h3 class=\"wp-block-heading\">Port 465: prv\u00e9 bezpe\u010dn\u00e9 rie\u0161enie (SMTPS)<\/h3>\n\n\n\n<p>Koncom 90. rokov bolo jasn\u00e9, \u017ee e-mail potrebuje \u0161ifrovanie. Objavil sa <strong>port 465<\/strong> s <strong>SMTPS<\/strong> (SMTP over SSL), kde sa \u0161ifrovan\u00fd tunel vytv\u00e1ra okam\u017eite pri pripojen\u00ed. Tomu sa hovor\u00ed <strong>Implicit SSL\/TLS<\/strong> \u2013 TLS handshake prebehne sk\u00f4r, ne\u017e sa odo\u0161l\u00fa SMTP pr\u00edkazy.<\/p>\n\n\n\n<p>Historicky to bolo roz\u0161\u00edren\u00e9, hoci ist\u00fd \u010das to nebolo ofici\u00e1lne \u0161tandardizovan\u00e9 cez IETF (organiz\u00e1cia pre internetov\u00e9 \u0161tandardy) a bolo to kr\u00e1tko ozna\u010dovan\u00e9 ako \u201edeprecated\u201c v prospech STARTTLS.<\/p>\n\n\n\n<p>V praxi v\u0161ak port 465 spravil ve\u013ek\u00fd comeback. Dnes je znovu akceptovan\u00fd, bezpe\u010dn\u00fd a extr\u00e9mne popul\u00e1rny. Viacer\u00ed ve\u013ek\u00ed poskytovatelia, vr\u00e1tane Gmailu, ho st\u00e1le odpor\u00fa\u010daj\u00fa. Pre web je to \u00faplne validn\u00e1 vo\u013eba.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Port 587: modern\u00fd \u0161tandard pre submission (STARTTLS)<\/h3>\n\n\n\n<p>Aby sa vyrie\u0161ila \u0161tandardiz\u00e1cia, IETF ur\u010dila <strong>port 587<\/strong> ako ofici\u00e1lny port pre <em>email submission<\/em> (t. j. odosielanie z klienta alebo webu). Tento port pou\u017e\u00edva \u0161ifrovanie cez <strong>STARTTLS<\/strong>, teda <strong>Explicit TLS<\/strong>.<\/p>\n\n\n\n<p>Mechanika STARTTLS vyzer\u00e1 zjednodu\u0161ene takto:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Web sa pripoj\u00ed na mail server cez port 587 najprv v plain texte.<\/li>\n\n\n<li>Po\u0161le pr\u00edkaz <code>EHLO<\/code> (pozdrav a identifik\u00e1cia).<\/li>\n\n\n<li>Server odpovie zoznamom schopnost\u00ed vr\u00e1tane <code>STARTTLS<\/code>.<\/li>\n\n\n<li>Klient po\u0161le pr\u00edkaz <code>STARTTLS<\/code> a t\u00fdm po\u017eiada o \u201eupgrade\u201c spojenia.<\/li>\n\n\n<li>Vytvor\u00ed sa TLS tunel a a\u017e potom sa posielaj\u00fa prihlasovacie \u00fadaje a samotn\u00fd e-mail.<\/li>\n\n<\/ol>\n\n\n\n<p>V roku 2026 je port 587 s nevyn\u00faten\u00fdm \u0161ifrovan\u00edm pova\u017eovan\u00fd za nebezpe\u010dn\u00fd; seri\u00f3zni poskytovatelia \u0161ifrovanie na submission portoch vynucuj\u00fa.<\/p>\n\n\n\n<p>Port 587 je dnes najodpor\u00fa\u010danej\u0161\u00ed a najroz\u0161\u00edrenej\u0161\u00ed \u0161tandard na odosielanie z webu.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Port 2525: ne\u0161tandardn\u00fd fallback<\/h3>\n\n\n\n<p>Ob\u010das naraz\u00ed\u0161 aj na <strong>port 2525<\/strong>. Nie je to ofici\u00e1lny SMTP port; je to alternat\u00edvny port, ktor\u00fd ve\u013ea SMTP slu\u017eieb podporuje ako z\u00e1lohu.<\/p>\n\n\n\n<p>Pou\u017e\u00edva sa v situ\u00e1cii, ke\u010f hosting blokuje port 587 aj 465. Je to sk\u00f4r rarita, ale st\u00e1va sa to \u2013 napr\u00edklad niektor\u00e9 cloud platformy blokuj\u00fa 587 kv\u00f4li prevencii spamu a n\u00fatia pou\u017ei\u0165 dedikovan\u00fd relay, ktor\u00fd po\u010d\u00fava pr\u00e1ve na 2525. Typicky ide op\u00e4\u0165 o STARTTLS podobne ako na 587.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verdikt pre rok 2026: ktor\u00fd SMTP port pou\u017ei\u0165?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Prim\u00e1rna vo\u013eba: port 587 (STARTTLS)<\/h3>\n\n\n\n<p>Toto je prv\u00e1 vo\u013eba. Je to modern\u00fd, ofici\u00e1lny \u0161tandard pre e-mail submission, podporuje ho prakticky ka\u017ed\u00fd SMTP provider a je navrhnut\u00fd presne na to, \u010do web potrebuje. Pou\u017e\u00edva \u0161ifrovanie STARTTLS (Explicit TLS).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Sekund\u00e1rna vo\u013eba: port 465 (SMTPS)<\/h3>\n\n\n\n<p>Ak 587 zlyh\u00e1 (napr. blokovanie portu, \u0161pecifick\u00e9 nastavenia siete) alebo ho poskytovate\u013e v\u00fdslovne odpor\u00fa\u010da (napr. Gmail\/Google Workspace), port 465 je v\u00fdborn\u00e1 a bezpe\u010dn\u00e1 alternat\u00edva. Pou\u017e\u00edva SMTPS (Implicit TLS).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Takmer nikdy: port 25<\/h3>\n\n\n\n<p>Nepou\u017e\u00edvaj ho na odosielanie z webu. Modern\u00e9 prostredie ho \u010dasto blokuje. Je ur\u010den\u00fd pre server-to-server relay medzi MTA, nie pre webov\u00e9 aplik\u00e1cie, ktor\u00e9 odosielaj\u00fa transak\u010dn\u00e9 e-maily.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Porovnanie portov (preh\u013eadn\u00e1 tabu\u013eka)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li><strong>25<\/strong> &#8211; Protocol: SMTP &#8211; Security: \u017eiadna &#8211; Use: server-to-server relay &#8211; Pre web: <strong>NIE (hostingy\/ISP blokuj\u00fa)<\/strong><\/li>\n\n\n<li><strong>465<\/strong> &#8211; Protocol: SMTPS &#8211; Security: <strong>Implicit SSL\/TLS<\/strong> &#8211; Use: client-to-server submission &#8211; Pre web: <strong>\u00c1no (bezpe\u010dn\u00e9 a be\u017en\u00e9)<\/strong><\/li>\n\n\n<li><strong>587<\/strong> &#8211; Protocol: SMTP &#8211; Security: <strong>Explicit (STARTTLS)<\/strong> &#8211; Use: client-to-server submission &#8211; Pre web: <strong>\u00c1NO (odpor\u00fa\u010dan\u00fd \u0161tandard)<\/strong><\/li>\n\n\n<li><strong>2525<\/strong> &#8211; Protocol: SMTP &#8211; Security: Explicit (STARTTLS) &#8211; Use: fallback submission &#8211; Pre web: <strong>len ke\u010f 587\/465 s\u00fa blokovan\u00e9<\/strong><\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Ako opravi\u0165 e-maily vo WordPresse: postup krok za krokom<\/h2>\n\n\n\n<p>Ke\u010f u\u017e vie\u0161, ktor\u00fd port m\u00e1 zmysel, po\u010fme na praktick\u00fd setup. Cie\u013e je jednoduch\u00fd: WordPress m\u00e1 presta\u0165 posiela\u0165 po\u0161tu cez <code>wp_mail()<\/code> \u201enapriamo\u201c a m\u00e1 ju presmerova\u0165 cez d\u00f4veryhodn\u00fa transak\u010dn\u00fa e-mail slu\u017ebu.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Krok 1: vyber dedikovan\u00e9ho SMTP\/transactional providera<\/h3>\n\n\n\n<p>Prv\u00fd krok je presta\u0165 pou\u017e\u00edva\u0165 webserver na odosielanie. Potrebuje\u0161 \u00fa\u010det u poskytovate\u013ea, ktor\u00fd sa \u0161pecializuje na doru\u010dite\u013enos\u0165 transak\u010dn\u00fdch e-mailov.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>\u010co robia: poskytuj\u00fa profesion\u00e1lny mail server s reput\u00e1ciou, cez ktor\u00fd m\u00f4\u017ee\u0161 posiela\u0165 e-maily (cez API alebo SMTP).<\/li>\n\n\n<li>Popul\u00e1rni poskytovatelia: SendGrid, Brevo (predt\u00fdm Sendinblue), Mailgun, Postmark (zn\u00e1my ve\u013emi vysokou doru\u010dite\u013enos\u0165ou), Amazon SES (v\u00fdkonn\u00e9, ale zlo\u017eitej\u0161ie), Google Workspace \/ Gmail (na n\u00edzky objem sa d\u00e1, ale pre biznis sa neodpor\u00fa\u010da kv\u00f4li limitom odosielania).<\/li>\n\n<\/ul>\n\n\n\n<p>Zvy\u010dajne ti bude sta\u010di\u0165 free tier \u2013 pokia\u013e ide o transak\u010dn\u00e9 e-maily men\u0161ieho a\u017e stredn\u00e9ho webu.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Krok 2: nastav DNS z\u00e1znamy dom\u00e9ny (SPF a DKIM)<\/h3>\n\n\n\n<p>Toto je najkritickej\u0161\u00ed technick\u00fd krok. Po v\u00fdbere providera mus\u00ed\u0161 svetu dok\u00e1za\u0165, \u017ee tento provider m\u00e1 povolenie odosiela\u0165 e-maily za tvoju dom\u00e9nu. Rob\u00ed sa to cez DNS z\u00e1znamy (tam, kde spravuje\u0161 DNS \u2013 registr\u00e1tor dom\u00e9ny alebo DNS hosting). Provider ti d\u00e1 presn\u00e9 hodnoty na skop\u00edrovanie.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li><strong>SPF (Sender Policy Framework):<\/strong> TXT z\u00e1znam, ktor\u00fd funguje ako zoznam povolen\u00fdch odosielate\u013eov. Prij\u00edmac\u00edm serverom hovor\u00ed: \u201eE-maily z <code>moja-domena.sk<\/code> s\u00fa legit\u00edmne len vtedy, ke\u010f prich\u00e1dzaj\u00fa z t\u00fdchto IP\/zdrojov (napr. m\u00f4j server a SendGrid).\u201c Chr\u00e1ni pred spoofingom (fal\u0161ovan\u00edm odosielate\u013ea).<\/li>\n\n\n<li><strong>DKIM (DomainKeys Identified Mail):<\/strong> TXT z\u00e1znam s verejn\u00fdm k\u013e\u00fa\u010dom, ktor\u00fd umo\u017en\u00ed overi\u0165 digit\u00e1lny podpis e-mailu. Provider podpisuje spr\u00e1vy s\u00fakromn\u00fdm k\u013e\u00fa\u010dom; prij\u00edmac\u00ed server over\u00ed podpis verejn\u00fdm k\u013e\u00fa\u010dom z tvojho DNS a zist\u00ed, \u017ee spr\u00e1va nebola po ceste pozmenen\u00e1.<\/li>\n\n<\/ul>\n\n\n\n<div class=\"wp-block-group callout callout-warning is-style-warning is-layout-flow wp-block-group-is-layout-flow\" style=\"border-width:1px;border-radius:8px;padding-top:1rem;padding-right:1.5rem;padding-bottom:1rem;padding-left:1.5rem\">\n\n<h4 class=\"wp-block-heading callout-title\">SPF a DKIM nie s\u00fa \u201enice to have\u201c<\/h4>\n\n\n<p>Bez SPF a DKIM ti nepom\u00f4\u017ee ani kvalitn\u00fd SMTP provider \u2013 e-maily bud\u00fa st\u00e1le vyzera\u0165 podozrivo a \u010dasto skon\u010dia v spame.<\/p>\n\n<\/div>\n\n\n\n<h3 class=\"wp-block-heading\">Krok 3: nain\u0161taluj a nastav SMTP plugin vo WordPresse<\/h3>\n\n\n\n<p>Teraz mus\u00ed\u0161 WordPressu poveda\u0165, aby pou\u017e\u00edval nov\u00fd sp\u00f4sob odosielania. Najjednoduch\u0161ie je pou\u017ei\u0165 plugin, ktor\u00fd zachyt\u00ed volania <code>wp_mail()<\/code> a presmeruje ich cez tvojho providera.<\/p>\n\n\n\n<p>Be\u017en\u00e9 pluginy:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>WP Mail SMTP<\/li>\n\n\n<li>FluentSMTP<\/li>\n\n\n<li>Post SMTP<\/li>\n\n<\/ul>\n\n\n\n<p>V\u0161etky funguj\u00fa podobne. Typick\u00e9 nastavenie:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Nain\u0161taluj a aktivuj vybran\u00fd SMTP plugin.<\/li>\n\n\n<li>Otvor jeho nastavenia v administr\u00e1cii WordPressu.<\/li>\n\n\n<li>Vyber \u201eMailer\u201c (napr. SendGrid).<\/li>\n\n\n<li>Zadaj prihlasovacie \u00fadaje:<\/li>\n\n\n<li>\u2013 Preferovan\u00e1 cesta je <strong>API<\/strong> (API key): bezpe\u010dnej\u0161ie a spo\u013eahlivej\u0161ie, provider ti d\u00e1 k\u013e\u00fa\u010d na vlo\u017eenie.<\/li>\n\n\n<li>\u2013 Alternat\u00edva je \u201eOther SMTP\u201c: zad\u00e1va\u0161 SMTP login ru\u010dne.<\/li>\n\n\n<li>Ak ide\u0161 cez ru\u010dn\u00e9 SMTP nastavenie, nastav konkr\u00e9tne polo\u017eky:<\/li>\n\n\n<li>\u2013 <strong>SMTP Host:<\/strong> dod\u00e1 provider (napr. <code>smtp.sendgrid.net<\/code>).<\/li>\n\n\n<li>\u2013 <strong>Encryption:<\/strong> vyber <strong>TLS<\/strong> (\u010do v tomto kontexte znamen\u00e1 STARTTLS). Ak je k dispoz\u00edcii len SSL\/SMTPS, je to vo\u013eba pre port 465.<\/li>\n\n\n<li>\u2013 <strong>SMTP Port:<\/strong> <strong>587<\/strong> pre TLS\/STARTTLS alebo <strong>465<\/strong> pre SMTPS\/SSL.<\/li>\n\n\n<li>\u2013 <strong>Authentication:<\/strong> zapni (ON).<\/li>\n\n\n<li>\u2013 <strong>SMTP Username:<\/strong> dod\u00e1 provider.<\/li>\n\n\n<li>\u2013 <strong>SMTP Password:<\/strong> dod\u00e1 provider.<\/li>\n\n\n<li>Nastav \u201eFrom\u201c \u00fadaje:<\/li>\n\n\n<li>\u2013 <strong>From Email:<\/strong> mus\u00ed by\u0165 z autentifikovanej dom\u00e9ny.<\/li>\n\n\n<li>\u2013 <strong>From Name:<\/strong> n\u00e1zov webu\/firmy.<\/li>\n\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Krok 4: otestuj odosielanie a sleduj logy<\/h3>\n\n\n\n<p>V\u00e4\u010d\u0161ina SMTP pluginov m\u00e1 z\u00e1lo\u017eku \u201eTest Email\u201c. Po\u0161li test na svoj Gmail alebo Outlook.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Ak doraz\u00ed do inboxu: konfigur\u00e1cia je v poriadku, posiela\u0161 autentifikovane.<\/li>\n\n\n<li>Ak skon\u010d\u00ed v spame: skontroluj SPF a DKIM (a po\u010d\u00edtaj s t\u00fdm, \u017ee DNS sa m\u00f4\u017ee propagova\u0165 aj nieko\u013eko hod\u00edn).<\/li>\n\n\n<li>Ak sa v\u00f4bec neodo\u0161le: typicky ide o chybu portu alebo prihlasovac\u00edch \u00fadajov. Skontroluj host, port, username a password. Sk\u00fas prepn\u00fa\u0165 587\u2194465 spolu so spr\u00e1vnym typom \u0161ifrovania (TLS\/STARTTLS vs. SSL\/SMTPS).<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">\u201eJednoduch\u00e9\u201c rie\u0161enie: ako to dnes rie\u0161ia modern\u00e9 WordPress platformy<\/h2>\n\n\n\n<p>\u0160tvor-krokov\u00fd setup vy\u0161\u0161ie je pre majite\u013ea be\u017en\u00e9ho biznis webu \u010dasto prive\u013ea: rie\u0161i\u0165 dom\u00e9nu, DNS, providera, API k\u013e\u00fa\u010de a WordPress pluginy naraz. Preto vznikaj\u00fa integrovan\u00e9 platformy, ktor\u00e9 tieto \u201emust-have\u201c slu\u017eby zabalili do jednej sk\u00fasenosti.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Rie\u0161enie 1: integrovan\u00fd transak\u010dn\u00fd e-mail (najjednoduch\u0161ia cesta)<\/h3>\n\n\n\n<p>Jadro probl\u00e9mu WordPress e-mailov je neautentifikovan\u00e9 odosielanie. Najjednoduch\u0161\u00ed sp\u00f4sob je pou\u017ei\u0165 slu\u017ebu, ktor\u00e1 default ob\u00edde bez zlo\u017eitej konfigur\u00e1cie.<\/p>\n\n\n\n<p>Presne na to cieli <a href=\"https:\/\/elementor.com\/products\/site-mailer\">Site Mailer by Elementor<\/a> \u2013 plugin typu \u201ezero-configuration\u201c.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Ako funguje: nain\u0161taluje\u0161 a aktivuje\u0161 plugin.<\/li>\n\n\n<li>\u010co sprav\u00ed: automaticky presmeruje v\u0161etky transak\u010dn\u00e9 e-maily webu (kontaktn\u00e9 formul\u00e1re, WooCommerce notifik\u00e1cie, resety hesla a pod.) cez autentifikovan\u00fa slu\u017ebu s vysokou doru\u010dite\u013enos\u0165ou.<\/li>\n\n\n<li>Pre\u010do je to in\u00e9: nemus\u00ed\u0161 si zaklada\u0165 \u00fa\u010det u SendGrid, rie\u0161i\u0165 API k\u013e\u00fa\u010de, nastavova\u0165 SPF\/DKIM ani vybera\u0165 port. Funguje to \u201eout of the box\u201c.<\/li>\n\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Rie\u0161enie 2: managed hosting, ktor\u00fd po\u010d\u00edta so SMTP<\/h3>\n\n\n\n<p>Druh\u00e1 \u010das\u0165 probl\u00e9mu b\u00fdva samotn\u00fd hosting: niektor\u00e9 prostredia s\u00fa re\u0161trikt\u00edvne a porty pre odosielanie blokuj\u00fa. Kvalitn\u00fd managed WordPress hosting s t\u00fdm r\u00e1ta a vytv\u00e1ra podmienky, aby si best practices vedel zavies\u0165 bez boja so serverom.<\/p>\n\n\n\n<p>Ako pr\u00edklad sa uv\u00e1dza <a href=\"https:\/\/elementor.com\/hosting\">Elementor Hosting<\/a>, ktor\u00fd be\u017e\u00ed na cloud infra\u0161trukt\u00fare optimalizovanej na v\u00fdkon a typicky po\u010d\u00edta s t\u00fdm, \u017ee porty ako 587 s\u00fa dostupn\u00e9 pre SMTP pluginy. Pointa je stabiln\u00fd z\u00e1klad, na ktorom vie\u0161 nasadi\u0165 doru\u010dite\u013enos\u0165 pod\u013ea pravidiel.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Nad r\u00e1mec SMTP: z\u00e1sadn\u00fd rozdiel medzi transak\u010dn\u00fdm a marketingov\u00fdm e-mailom<\/h2>\n\n\n\n<p>Ke\u010f u\u017e m\u00e1\u0161 webov\u00e9 e-maily opraven\u00e9, prich\u00e1dza jedno pravidlo, ktor\u00e9 si zasl\u00fa\u017ei tu\u010dn\u00e9 p\u00edsmo: neposielaj newslettery cez transak\u010dn\u00fa SMTP slu\u017ebu.<\/p>\n\n\n\n<p>Tvoje SendGrid\/Brevo\/Mailgun (alebo aj Site Mailer) je ur\u010den\u00e9 prim\u00e1rne na <strong>transak\u010dn\u00e9 e-maily<\/strong> \u2013 teda spr\u00e1vy 1:1 sp\u00fa\u0161\u0165an\u00e9 akciou pou\u017e\u00edvate\u013ea.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Transak\u010dn\u00e9 e-maily (pou\u017ei SMTP\/transactional provider): reset hesla, potvrdenie objedn\u00e1vky, potvrdenie registr\u00e1cie, potvrdenie odoslania formul\u00e1ra, welcome e-mail. S\u00fa o\u010dak\u00e1van\u00e9 a kritick\u00e9, musia skon\u010di\u0165 v inboxe.<\/li>\n\n\n<li>Marketingov\u00e9 e-maily (pou\u017ei ESP \u2013 Email Service Provider): newsletter, promo kampane, oznamy o nov\u00fdch produktoch. S\u00fa hromadn\u00e9 (1:N) a prin\u00e1\u0161aj\u00fa odhl\u00e1senia a spam complainty.<\/li>\n\n<\/ul>\n\n\n\n<p>Ak po\u0161le\u0161 10 000-pr\u00edjemcov newsletter cez transak\u010dn\u00fa slu\u017ebu, zv\u00fd\u0161i\u0161 odhl\u00e1senia a s\u0165a\u017enosti na spam. To vie zni\u010di\u0165 reput\u00e1ciu dom\u00e9ny a n\u00e1sledne za\u010dn\u00fa pada\u0165 do spamu aj tvoje transak\u010dn\u00e9 e-maily (napr. reset hesla). Preto marketing v\u017edy rie\u0161 cez n\u00e1stroje typu Mailchimp alebo ConvertKit, ktor\u00e9 s\u00fa na bulk sending, odhl\u00e1senia a reput\u00e1ciu stavan\u00e9.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Odpor\u00fa\u010dan\u00e1 e-mail strat\u00e9gia pre web v roku 2026<\/h2>\n\n\n\n<p>Ak to zhrniem do praktickej strat\u00e9gie, m\u00e1 tri \u010dasti:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Stabiln\u00fd z\u00e1klad: kvalitn\u00fd hosting, ktor\u00fd ti neblokuje implement\u00e1ciu best practices (napr. otvoren\u00e9 relevantn\u00e9 porty pre SMTP).<\/li>\n\n\n<li>Spo\u013eahliv\u00e9 transak\u010dn\u00e9 odosielanie: bu\u010f \u201ezero-config\u201c pr\u00edstup cez <a href=\"https:\/\/elementor.com\/products\/site-mailer\">Site Mailer by Elementor<\/a>, alebo klasick\u00fd setup (napr. WP Mail SMTP + provider) s preferenciou <strong>portu 587<\/strong>.<\/li>\n\n\n<li>Samostatn\u00fd marketingov\u00fd kan\u00e1l: pou\u017e\u00edvanie dedikovanej email marketing platformy (ESP) pre newslettery a kampane, aby sa chr\u00e1nila reput\u00e1cia transak\u010dn\u00e9ho odosielania.<\/li>\n\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Z\u00e1ver: presta\u0148 str\u00e1ca\u0165 e-maily a oprav d\u00f4veru<\/h2>\n\n\n\n<p>Ot\u00e1zka \u201ektor\u00fd SMTP port pou\u017ei\u0165\u201c je dobr\u00fd za\u010diatok a odpove\u010f je v roku 2026 jasn\u00e1: <strong>port 587<\/strong>.<\/p>\n\n\n\n<p>Z\u00e1rove\u0148 v\u0161ak plat\u00ed, \u017ee samotn\u00fd port je len \u010das\u0165 sklada\u010dky. Podstatn\u00e9 je zmeni\u0165 sp\u00f4sob, ak\u00fdm web posiela e-maily: presta\u0165 sa spolieha\u0165 na <code>wp_mail()<\/code> a prejs\u0165 na autentifikovan\u00fa, profesion\u00e1lnu transak\u010dn\u00fa slu\u017ebu \u2013 ide\u00e1lne so spr\u00e1vne nastaven\u00fdmi SPF a DKIM.<\/p>\n\n\n\n<p>Ke\u010f to sprav\u00ed\u0161, nerie\u0161i\u0161 len technick\u00fd detail. Buduje\u0161 komunika\u010dn\u00fd kan\u00e1l, ktor\u00fd je d\u00f4veryhodn\u00fd pre inbox providerov aj pre \u013eud\u00ed: objedn\u00e1vky s\u00fa potvrden\u00e9, resety hesla pr\u00eddu a leady z formul\u00e1rov nezmizn\u00fa v e-mailovom v\u00e1kuu.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ \u2013 naj\u010dastej\u0161ie ot\u00e1zky<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Ak\u00e1 je jednoduch\u00e1 odpove\u010f? Ktor\u00fd SMTP port m\u00e1m pou\u017ei\u0165?<\/h3>\n\n\n\n<p>Pou\u017ei <strong>port 587<\/strong> so \u0161ifrovan\u00edm <strong>STARTTLS<\/strong>. Ak to nefunguje, \u010fal\u0161ia najlep\u0161ia vo\u013eba je <strong>port 465<\/strong> so <strong>SMTPS<\/strong> (SSL\/TLS).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Pre\u010do by som nemal pou\u017e\u00edva\u0165 port 25?<\/h3>\n\n\n\n<p>Port 25 je p\u00f4vodn\u00fd ne\u0161ifrovan\u00fd SMTP port z roku 1982. Bol mas\u00edvne zneu\u017e\u00edvan\u00fd na spam, preto ho dnes blokuje v\u00e4\u010d\u0161ina reziden\u010dn\u00fdch ISP aj cloud hosting poskytovate\u013eov. Na odosielanie z webu sa na\u0148 ned\u00e1 spo\u013eahn\u00fa\u0165.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Ak\u00fd je rozdiel medzi portom 587 (STARTTLS) a 465 (SMTPS)?<\/h3>\n\n\n\n<p>Oba s\u00fa bezpe\u010dn\u00e9. <strong>Port 465<\/strong> pou\u017e\u00edva <em>Implicit TLS<\/em> \u2013 \u0161ifrovan\u00e9 spojenie za\u010dne okam\u017eite. <strong>Port 587<\/strong> pou\u017e\u00edva <em>Explicit TLS<\/em> cez pr\u00edkaz STARTTLS \u2013 spojenie sa najprv otvor\u00ed a n\u00e1sledne sa \u201eupgradne\u201c na \u0161ifrovan\u00e9. Port 587 je modern\u00fd odpor\u00fa\u010dan\u00fd \u0161tandard, ale oba funguj\u00fa.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. \u010co je \u201etransak\u010dn\u00fd e-mail\u201c?<\/h3>\n\n\n\n<p>Je to e-mail 1:1 spusten\u00fd akciou pou\u017e\u00edvate\u013ea na webe. Patria sem spr\u00e1vy z kontaktn\u00e9ho formul\u00e1ra, \u017eiadosti o reset hesla, registr\u00e1cie nov\u00fdch pou\u017e\u00edvate\u013eov a potvrdenia objedn\u00e1vok v eCommerce. Toto posielaj cez dedikovan\u00fa SMTP\/transak\u010dn\u00fa slu\u017ebu.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5. Ako sa transak\u010dn\u00fd e-mail l\u00ed\u0161i od marketingov\u00e9ho e-mailu?<\/h3>\n\n\n\n<p>Marketingov\u00fd e-mail je hromadn\u00e9 vysielanie 1:N (newsletter, promo, oznamy). Na to potrebuje\u0161 samostatn\u00fa platformu (ESP), aby si si nepo\u0161kodil reput\u00e1ciu odosielania a neohrozil transak\u010dn\u00e9 e-maily.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. \u010co s\u00fa SPF a DKIM a naozaj ich potrebujem?<\/h3>\n\n\n\n<p>\u00c1no, naozaj ich potrebuje\u0161. S\u00fa to DNS z\u00e1znamy, ktor\u00e9 dokazuj\u00fa legitimitu e-mailov. <strong>SPF<\/strong> je zoznam serverov, ktor\u00e9 m\u00f4\u017eu odosiela\u0165 po\u0161tu za tvoju dom\u00e9nu. <strong>DKIM<\/strong> je digit\u00e1lny podpis, ktor\u00fd over\u00ed, \u017ee spr\u00e1va nebola pozmenen\u00e1. Bez nich bud\u00fa e-maily p\u00f4sobi\u0165 ako spam.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7. SMTP plugin odo m\u0148a chce \u201eHost\u201c. \u010co to je?<\/h3>\n\n\n\n<p>\u201eHost\u201c je adresa SMTP servera tvojho providera. Napr\u00edklad SendGrid pou\u017e\u00edva <code>smtp.sendgrid.net<\/code> a Google <code>smtp.gmail.com<\/code>. Presn\u00fa hodnotu ti poskytne provider.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">8. M\u00f4\u017eem posiela\u0165 webov\u00e9 e-maily cez svoj be\u017en\u00fd Gmail \u00fa\u010det?<\/h3>\n\n\n\n<p>Technicky \u00e1no, ale neodpor\u00fa\u010da sa to. V administr\u00e1cii WordPressu by si rie\u0161il osobn\u00e9 prihlasovacie \u00fadaje (bezpe\u010dnostn\u00e9 riziko) a Google m\u00e1 pr\u00edsne sending limity \u2013 pri \u0161pi\u010dke m\u00f4\u017ee \u00fa\u010det do\u010dasne zablokova\u0165. Pre seri\u00f3zny web je lep\u0161\u00ed dedikovan\u00fd provider.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9. Ak\u00fd je najjednoduch\u0161\u00ed sp\u00f4sob, ako opravi\u0165 v\u0161etky WordPress e-mail probl\u00e9my?<\/h3>\n\n\n\n<p>Pou\u017ei\u0165 \u201ezero-configuration\u201c plugin ako <a href=\"https:\/\/elementor.com\/products\/site-mailer\">Site Mailer by Elementor<\/a>, ktor\u00fd po aktiv\u00e1cii presmeruje transak\u010dn\u00e9 e-maily a rie\u0161i doru\u010dite\u013enos\u0165 bez toho, aby si nastavoval porty, API k\u013e\u00fa\u010de alebo slu\u017eby tret\u00edch str\u00e1n.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">10. Ako otestujem, \u017ee SMTP nastavenie funguje?<\/h3>\n\n\n\n<p>Kvalitn\u00e9 SMTP pluginy (napr. WP Mail SMTP) maj\u00fa v nastaveniach \u201eTest Email\u201c. Po\u0161li test z WordPress administr\u00e1cie na svoj e-mail. Ak doraz\u00ed do inboxu, m\u00e1\u0161 hotovo.<\/p>\n\n\n<div class=\"references-section\">\n                <h2>Referencie \/ Zdroje<\/h2>\n                <ul class=\"references-list\"><li><a href=\"https:\/\/elementor.com\/blog\/smtp-ports-explained\/\" target=\"_blank\" rel=\"noopener noreferrer\">SMTP Ports Explained: The Right Choice for Email Deliverability in 2026<\/a><\/li><\/ul>\n            <\/div>","protected":false},"excerpt":{"rendered":"<p>Kontaktn\u00fd formul\u00e1r, reset hesla alebo potvrdenie objedn\u00e1vky, ktor\u00e9 nikdy nedoraz\u00ed, je tich\u00fd zabijak konverzi\u00ed. Vysvetl\u00edm, ktor\u00e9 SMTP porty dnes naozaj d\u00e1vaj\u00fa zmysel a ako nastavi\u0165 WordPress e-maily tak, aby boli doru\u010dite\u013en\u00e9 a d\u00f4veryhodn\u00e9.<\/p>\n","protected":false},"author":36,"featured_media":191,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[49],"tags":[37,119,118,5,10],"class_list":["post-192","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ekosystem-wordpress","tag-bezpecnost","tag-dns","tag-email-deliverability","tag-smtp","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/posts\/192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/users\/36"}],"replies":[{"embeddable":true,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/comments?post=192"}],"version-history":[{"count":0,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/posts\/192\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/media\/191"}],"wp:attachment":[{"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/media?parent=192"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/categories?post=192"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/tags?post=192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}