{"id":52639,"date":"2019-11-13T00:00:00","date_gmt":"2019-11-12T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/domen-fronting-na-baze-tls-1-3"},"modified":"2026-05-20T19:54:20","modified_gmt":"2026-05-20T17:54:20","slug":"domen-fronting-na-baze-tls-1-3","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/domen-fronting-na-baze-tls-1-3","title":{"rendered":"Domeeni fronting TLS 1.3 baasil","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sissejuhatus<\/h3>\n

\"Domeeni
\nKaasaegsed ettev\u00f5tte sisu filtreerimise s\u00fcsteemid tuntud tootjatelt nagu Cisco, BlueCoat, FireEye sarnanevad oma v\u00f5imsamate kolleegidega - DPI s\u00fcsteemidega, mida kohalikul tasandil laialdaselt juurutatakse. Nende ja teiste t\u00f6\u00f6p\u00f5him\u00f5te seisneb siseneva ja v\u00e4ljuva internetiliikluse kontrollimises ning mustade\/valgete nimekirjade p\u00f5hjal interneti\u00fchenduste keelamise otsuste tegemises. Kuna nii need kui ka teised tuginevad oma toimimisel sarnastele p\u00f5him\u00f5tetele, on k\u00e4igud nende \u00fcletamiseks samuti sarnased.<\/p>\n

\u00dcks tehnoloogiaid, mis v\u00f5imaldab t\u00f5husalt nii DPI-d kui ka ettev\u00f5tte s\u00fcsteeme \u00fcletada, on domeeni fronting tehnoloogia. Selle p\u00f5hiolemus seisneb selles, et me p\u00e4\u00e4seme blokeeritud ressursile, kasutades teist, avalikku domeeni, millel on hea maine ja mida ei blokeeri mingisugune s\u00fcsteem, n\u00e4iteks google.com.<\/p>\n

Selle tehnoloogia kohta on kirjutatud piisavalt palju artikleid ja toodud palju n\u00e4iteid. Siiski pakuvad hiljuti populaarsust kogunud tehnoloogiad DNS-over-HTTPS ja encrypted-SNI, samuti uus TLS 1.3 protokolli versioon v\u00f5imaluse k\u00e4sitleda veel \u00fcht domeeni fronting varianti.
\n<\/a><\/p>\n

Selgitame v\u00e4lja tehnoloogia<\/h3>\n

Alustame olulisemate terminite selgitamisest, et iga\u00fchel oleks arusaam, kes on kes ja miks on see vajalik. Mainisime mehhanismi eSNI, mille toimimist k\u00e4sitletakse allpool. eSNI (encrypted Server Name Indication) mehhanism on SNI kaitstud versioon, mis on saadaval ainult TLS 1.3 protokollile. P\u00f5hiolemus on kr\u00fcpteerida muu hulgas teave, millise domeeni poole p\u00e4ring saadetakse.<\/p>\n

N\u00fc\u00fcd vaatame eSNI mehhanismi toimimist praktikas.<\/p>\n

Oletame, et meil on internetiresurss, mida blokeerib kaasaegne DPI lahendus (v\u00f5tame n\u00e4iteks tuntud torrent-tracker'i - rutracker.nl). Kui proovime p\u00e4\u00e4seda torrent-tracker'i saidile - n\u00e4eme teenusepakkuja standardset teavitust, et ressurss on blokeeritud:<\/p>\n

\"Domeeni<\/p>\n

RKNi saidil on see domeen t\u00f5epoolest stopp-nimekirjades:<\/p>\n

\"Domeeni<\/p>\n

Whois p\u00e4ringu p\u00f5hjal on n\u00e4ha, et domeen on 'peidetud' pilvprovideri Cloudflare'i taha.<\/p>\n

\"Domeeni<\/p>\n

Kuid erinevalt RKNi \"spetsialistidest\" ei hakanud Beeline'i rohkem tehniliselt haritud t\u00f6\u00f6tajad (v\u00f5i siis meie tuntud regulaatori kibeda kogemuse t\u00f5ttu) lihtsalt IP-aadressi j\u00e4rgi veebisaiti blokeerima, vaid lisasid bloki nimekirja just domeeninime<\/a>. Sellele on lihtne veenduda, kui vaadata, millised veel domeenid peituvad selle sama IP-aadress<\/a>, k\u00fclastada \u00fchte neist ja n\u00e4ha, et ligip\u00e4\u00e4s ei ole blokeeritud:<\/p>\n

\"Domeeni<\/p>\n

Kuidas see siis nii juhtub? Kuidas pakkuja DPI teab, millisele domeenile minu brauser suundub, kui k\u00f5ik suhtlused toimuvad https-protokolli kaudu, ja Beeline'i https-sertifikaatide asendamist me seni ei ole t\u00e4heldanud? Kas ta on selgeltn\u00e4gija v\u00f5i j\u00e4lgib keegi mind?<\/p>\n

Proovime sellele k\u00fcsimusele vastata, vaadates liiklust l\u00e4bi Wiresharki<\/p>\n

\"Domeeni<\/p>\n

Kuvamisel on n\u00e4ha, et k\u00f5igepealt saab brauser serveri IP-aadressi DNS-i kaudu, seej\u00e4rel toimub standardne TCP-k\u00e4epigistus sihtserveriga ja siis p\u00fc\u00fcab brauser luua ssl-\u00fchendust serveriga. Selleks edastab ta paketi SSL<\/a> Client Hello, milles on originaaldomeeni nimi avatud kujul. See v\u00e4li on vajalik Cloudflare'i frontend-serverile, et \u00f5igesti marsruutida \u00fchendus. Just siin p\u00fc\u00fcab meid kinni pakkuja DPI, katkestades meie \u00fchenduse. Me ei saa pakkuja poolt mingeid blokeeringuteavet ja n\u00e4eme tavalist brauseri viga, nagu oleks sait v\u00e4lja l\u00fclitatud v\u00f5i ei t\u00f6\u00f6taks lihtsalt:<\/p>\n

\"Domeeni<\/p>\n

N\u00fc\u00fcd aktiveerime brauseris eSNI mehhanismi, nagu on kirjas juhendis Firefox <\/a>:
\nSelleks avame Firefoxi konfigureerimise lehe about:config<\/b> ja aktiveerime j\u00e4rgmised seaded:<\/p>\n

network.trr.mode = 2;\nnetwork.trr.uri = https:\/\/mozilla.cloudflare-dns.com\/dns-query\nnetwork.security.esni.enabled = true\n<\/code><\/pre>\n
P\u00e4rast seda kontrollime seadete \u00f5igsust Cloudflare'i saidil lingil<\/a> ja proovime veel kord meie torrent-trackeriga sama trikki.<\/p>\n
\"Domeeni<\/p>\n
Voila. Meie lemmik-tracker avanes, ilma igasuguste VPN-ide ja proksiserveriteta. Vaadakem n\u00fc\u00fcd Wiresharki liiklusdampi, mis juhtus.<\/p>\n
\"Domeeni<\/p>\n
Seekord ei sisalda ssl client hello pakett sihtdomeeni selgelt, vaid paketi sees on uus v\u00e4li \u2014 encrypted_server_name \u2014 just seal on v\u00e4\u00e4rtus rutracker.nl ja seda v\u00e4lja saab dekr\u00fcpteerida ainult Cloudflare'i frontend-server. Kui nii on, siis ei j\u00e4\u00e4 pakkuja DPI-le muud \u00fcle, kui k\u00e4si pesta ja sellist liiklust lubada. Ja teisi \u0161ifreerimisv\u00f5imalusi ei olegi.<\/p>\n
Nii et, kuidas tehnoloogia brauseris t\u00f6\u00f6tab \u2014 me vaatasime. N\u00fc\u00fcd proovime seda rakendada konkreetsematesse ja huvitavatesse asjadesse. Alguseks \u00f5petame, kuidas kasutada seda sama curl eSNI abil TLS 1.3-tal, ja vaatame, kuidas toimib domeenifronting eSNI p\u00f5hjal.<\/p>\n
Domeenifronting eSNI-ga<\/h3>\n
Kuna curl kasutab https-protokolliga \u00fchendamiseks standardset openssl teeki, peame k\u00f5igepealt tagama eSNI toe just seal. OpenSSL-i master-harudes pole eSNI toe jaoks veel olemas, seega peame alla laadima spetsiaalse avatud haru openssl-ist, selle kompileerima ja installima.<\/p>\n
Kloonime repot gitHubist ja kompileerime nagu tavaliselt:<\/p>\n
$ git clone https:\/\/github.com\/sftcd\/openssl\n$ cd openssl\n$ .\/config\n\n$ make\n$ cd esnistuff\n$ make\n<\/code><\/pre>\n
Seej\u00e4rel kloonime curl'i repot ja konfigureerime selle kompileerimise, kasutades meie koostatud openssl teeki:<\/p>\n
$ cd $HOME\/code\n$ git clone https:\/\/github.com\/niallor\/curl.git curl-esni\n$ cd curl-esni\n\n$ export LD_LIBRARY_PATH=\/opt\/openssl\n$ .\/buildconf\n$ LDFLAGS=\"-L\/opt\/openssl\" .\/configure --with-ssl=\/opt\/openssl --enable-esni --enable-debug\n<\/code><\/pre>\n
Siin on oluline \u00f5igesti m\u00e4\u00e4rata k\u00f5ik kataloogid, kus openssl asub (meie puhul \u2014 see on \/opt\/openssl\/) ja veenduda, et konfiguratsiooniprotsess ei sisaldaks vigu.<\/p>\n
Juhul kui konfiguratsioon \u00f5nnestub \u2014 n\u00e4eme rida:<\/p>\n
WARNING: esni ESNI enabled but marked EXPERIMENTAL. Use with caution!<\/b><\/p>\n
$ make<\/code><\/pre>\n
P\u00e4rast paketi edukat koostamist kasutame openssl-ist saadud spetsiaalset bash-faili curl'i seadistamiseks ja k\u00e4ivitamiseks. Kopeerime selle curl'i katalooge mugavuse huvides:<\/p>\n
cp \/opt\/openssl\/esnistuff\/curl-esni <\/code><\/pre>\n
ja sooritame testimise https-p\u00e4ringu cloudflare serverisse, salvestades samal ajal DNS ja TLS paketid Wireshark'i.<\/p>\n
$ ESNI_COVER=\"www.hello-rkn.ru\" .\/curl-esni https:\/\/cloudflare.com\/<\/code><\/pre>\n
Serveri vastuses koos hulga silumisinfoga openssl'ist ja curl'ist saame HTTP vastuse koodiga 301 cloudflare'ilt.<\/p>\n
HTTP\/1.1 301 Moved Permanently\n<Date: Sun, 03 Nov 2019 13:12:55 GMT\n<Transfer-Encoding: chunked\n<Connection: keep-alive\n<Cache-Control: max-age=3600\n<Expires: Sun, 03 Nov 2019 14:12:55 GMT\n<Location: https:\/\/www.cloudflare.com\/\n<\/code><\/pre>\n
mis t\u00f5endab, et meie p\u00e4ring on edukalt toimetatud sihtserverisse, kuulatud ja t\u00f6\u00f6deldud.<\/p>\n
N\u00fc\u00fcd vaatame liikluse dumpi wireshark'is, st mida n\u00e4gi antud juhul teenuseliini DPI.<\/p>\n
\"Domeeni<\/p>\n
On n\u00e4ha, et esmalt p\u00f6\u00f6rdus curl DNS-serveri poole, et saada Cloudflare'i serveri avalikke eSNI v\u00f5tmeid \u2013 TXT DNS p\u00e4ring _esni.cloudflare.com (pakett nr 13). Seej\u00e4rel saatis curl openssl-raamatukogu abil TLS 1.3 p\u00e4ringu Cloudflare'i serverisse, kus SNI v\u00e4li oli kr\u00fcpteeritud eelnevalt saadud avaliku v\u00f5tmega (pakett nr 22). Kuid peale eSNI v\u00e4lja sisaldas SSL-hello pakett ka tavalist avatud SNI v\u00e4lja, mille v\u00f5ime m\u00e4\u00e4rata suvalises j\u00e4rjekorras (antud juhul \u2013 www.hello-rkn.ru<\/a>). <\/b><\/p>\n
Seda avatud SNI v\u00e4lja ei arvestatud Cloudflare'i serverite poolt ja see oli vaid varjamine teenusepakkuja DPI jaoks. Cloudflare'i server aktsepteeris meie ssl-hello paketti, dekr\u00fcpteeris eSNI, eraldas sealt originaalse SNI ja k\u00e4sitles seda nagu mitte midagi (tehtud oli t\u00e4pselt nii, nagu eSNI loomisel plaanitud).<\/p>\n
Ainus, mille k\u00fclge siin DPI vaatenurgast kinni hakata, on esmase DNS p\u00e4ringu tegemine _esni.cloudflare.com. Kuid me tegime DNS p\u00e4ringu avatud ainult selleks, et n\u00e4idata, kuidas see mehhanism seestpoolt t\u00f6\u00f6tab.<\/p>\n
Kuna DPI alt l\u00f5plikult p\u00f5randat jalge alt v\u00e4lja t\u00f5mmata, kasutame juba mainitud DNS-over-HTTPS mehhanismi. V\u00e4ike selgitus - DOH - protokoll, mis v\u00f5imaldab kaitsta 'mees keset' r\u00fcnnaku eest, edastades DNS-p\u00e4ringu HTTPS protokolli kaudu.<\/p>\n
Teeme p\u00e4ringu uuesti, kuid seekord saame avalikud eSNI v\u00f5tmed HTTPS protokolli kaudu, mitte DNS-i kaudu:<\/p>\n
ESNI_COVER=\"www.hello-rkn.ru\" DOH_URL=https:\/\/mozilla.cloudflare-dns.com\/dns-query .\/curl-esni https:\/\/cloudflare.com\/<\/code><\/pre>\n
P\u00e4ringu liikluse dump on esitatud alloleval ekraanipildil:<\/p>\n
\"Domeeni<\/p>\n
On n\u00e4ha, et esmalt p\u00f6\u00f6rdub curl mozilla.cloudflare-dns.com serveri poole DoH protokolli kaudu (HTTPS \u00fchendus serveriga 104.16.249.249), et saada SNI kr\u00fcpteerimiseks vajalikke avalikke v\u00f5tmeid, ja seej\u00e4rel p\u00e4ring suunatakse sihtserverisse, varjates end samal ajal domeeniga. www.hello-rkn.ru<\/a>.<\/p>\n
Peale eespool nimetatud DoH resolveri mozilla.cloudflare-dns.com saame kasutada ka teisi populaarseid DoH teenuseid, n\u00e4iteks kurikuulsa kurjuse korporatsiooni teenuseid.
\nTeeme sellise p\u00e4ringu:<\/p>\n
ESNI_COVER=\"www.kremlin.ru\" DOH_URL=https:\/\/dns.google\/dns-query .\/curl-esni https:\/\/rutracker.nl\/<\/code><\/pre>\n
Ja saame vastuse:<\/p>\n
< HTTP\/1.1 301 Moved Permanently\n< Date: Sun, 03 Nov 2019 14:10:22 GMT\n< Content-Type: text\/html\n< Transfer-Encoding: chunked\n< Connection: keep-alive\n< Set-Cookie: __cfduid=da0144d982437e77b0b37af7d00438b1a1572790222; expires=Mon, 02-Nov-20 14:10:22 GMT; path=\/; domain=.rutracker.nl; HttpOnly; Secure\n< Location: https:\/\/rutracker.nl\/forum\/index.php\n< CF-Cache-Status: DYNAMIC\n< Expect-CT: max-age=604800, report-uri="https:\/\/report-uri.cloudflare.com\/cdn-cgi\/beacon\/expect-ct"\n< Server: cloudflare\n< CF-RAY: 52feee696f42d891-CPH\n<\/code><\/pre>\n
\"Domeeni<\/p>\n
Antud juhul p\u00f6\u00f6rdusime blokeeritud serveri rutracker.nl poole, kasutades DoH-resolvert dns.google (siin pole tr\u00fckiviga, n\u00fc\u00fcd on kuulsa korporatsiooni oma tippdomeen) ja varjasime end teise domeeni taha, mille blokeerimine on rangelt keelatud k\u00f5igile DPI-dele surmaohuga. Vastusest v\u00f5ib aru saada, et meie p\u00e4ring t\u00f6\u00f6tati edukalt \u00fcles.<\/p>\n
Lisakontrollina, et veenduda, et teenusepakkuja DPI reageerib avatud SNI-le, mida me varjatuna edastame \u2014 saame saata p\u00e4ringu rutracker.nl, varjades end mingi muu keelatud ressursi, n\u00e4iteks teise \"head\" torrent-kerija taha:<\/p>\n
$ ESNI_COVER=\"rutor.info\" DOH_URL=https:\/\/dns.google\/dns-query .\/curl-esni https:\/\/rutracker.nl\/<\/code><\/pre>\n
Me ei saa serverilt vastust, kuna meie p\u00e4ring blokeeritakse DPI-s\u00fcsteemi poolt.<\/p>\n
V\u00e4ike j\u00e4reldus esimesele osale<\/h3>\n
Nii et oleme suutnud demonstreerida eSNI toimivust openssl'i ja curl'i abil ning kontrollida eSNI-p\u00f5histe domeenifrontide t\u00f6\u00f6d. Sarnasel viisil saame kohandada oma lemmikinstrumente, mis kasutavad openssl'i teeki, et t\u00f6\u00f6tada \"varjatuna\" teiste domeenide taga. Rohkem sellest \u2014 meie j\u00e4rgnevates artiklites.<\/p>\n
Allikas: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0421\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0435 \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0442\u0438\u0432\u043d\u044b\u0435 \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0444\u0438\u043b\u044c\u0442\u0440\u0430\u0446\u0438\u0438 \u043a\u043e\u043d\u0442\u0435\u043d\u0442\u0430, \u043e\u0442 \u0442\u0430\u043a\u0438\u0445 \u0438\u043c\u0435\u043d\u0438\u0442\u044b\u0445 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u0435\u0439 \u043a\u0430\u043a Cisco, BlueCoat, FireEye \u0438\u043c\u0435\u044e\u0442 \u0434\u043e\u0432\u043e\u043b\u044c\u043d\u043e \u043c\u043d\u043e\u0433\u043e \u043e\u0431\u0449\u0435\u0433\u043e \u0441 \u0431\u043e\u043b\u0435\u0435 \u043c\u043e\u0449\u043d\u044b\u043c\u0438 \u0438\u0445 \u0441\u043e\u0431\u0440\u0430\u0442\u044c\u044f\u043c\u0438 \u2014 DPI \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u043c\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0443\u0441\u0438\u043b\u0435\u043d\u043d\u043e \u0432\u043d\u0435\u0434\u0440\u044f\u044e\u0442\u0441\u044f \u043d\u0430 \u043d\u0430\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u043e\u043c \u0443\u0440\u043e\u0432\u043d\u0435. \u0421\u0443\u0442\u044c \u0440\u0430\u0431\u043e\u0442\u044b \u0438 \u0442\u0435\u0445 \u0438 \u0434\u0440\u0443\u0433\u0438\u0445 \u0432 \u0442\u043e\u043c, \u0447\u0442\u043e\u0431\u044b \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u044c \u0434\u043e\u0441\u043c\u043e\u0442\u0440 \u0432\u0445\u043e\u0434\u044f\u0449\u0435\u0433\u043e \u0438 \u0438\u0441\u0445\u043e\u0434\u044f\u0449\u0435\u0433\u043e \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442 \u0442\u0440\u0430\u0444\u0438\u043a\u0430 \u0438, \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0430\u043d\u0438\u0438 \u0447\u0435\u0440\u043d\u044b\u0445\/\u0431\u0435\u043b\u044b\u0445 \u0441\u043f\u0438\u0441\u043a\u043e\u0432, \u043f\u0440\u0438\u043d\u0438\u043c\u0430\u0442\u044c \u0440\u0435\u0448\u0435\u043d\u0438\u0435 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-52639","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Domeenifront TLS 1.3 baasil | ProHoster","description":"Sissejuhatus Kaasaegsed ettev\u00f5tte filtratsioonis\u00fcsteemid.","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/domen-fronting-na-baze-tls-1-3","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0414\u043e\u043c\u0435\u043d-\u0444\u0440\u043e\u043d\u0442\u0438\u043d\u0433 \u043d\u0430 \u0431\u0430\u0437\u0435 TLS 1.3 | ProHoster","og:description":"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0421\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0435 \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0442\u0438\u0432\u043d\u044b\u0435 \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0444\u0438\u043b\u044c\u0442\u0440\u0430\u0446\u0438\u0438.","og:url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/domen-fronting-na-baze-tls-1-3","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-11-12T21:00:00+00:00","article:modified_time":"2026-05-20T17:54:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"52639","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-24 04:19:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 20:39:27","updated":"2026-01-24 04:19:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/52639","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=52639"}],"version-history":[{"count":3,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/52639\/revisions"}],"predecessor-version":[{"id":173323,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/52639\/revisions\/173323"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=52639"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=52639"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=52639"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}