{"id":1972,"date":"2026-08-18T16:35:19","date_gmt":"2026-08-18T13:35:19","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1972"},"modified":"2026-08-04T11:29:00","modified_gmt":"2026-08-04T11:29:00","slug":"wordpress-hsts-preload-avantajlari-ve-riskleri","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/wordpress-hsts-preload-avantajlari-ve-riskleri\/","title":{"rendered":"WordPress HSTS Preload: Avantajlar\u0131, Gereksinimleri ve Riskleri"},"content":{"rendered":"

HSTS preload, alan ad\u0131n\u0131n taray\u0131c\u0131lar\u0131n yerle\u015fik HTTPS listesine eklenmesini sa\u011flar. B\u00f6ylece ilk ziyarette bile HTTP ba\u011flant\u0131s\u0131 denenmez. Bunun kar\u015f\u0131l\u0131\u011f\u0131nda k\u00f6k alan\u0131n b\u00fct\u00fcn alt alanlar\u0131 i\u00e7in uzun vadeli HTTPS taahh\u00fcd\u00fc verilir.<\/p>\n

Preload bir g\u00fcvenlik puan\u0131 i\u00e7in a\u00e7\u0131lacak basit bir se\u00e7enek de\u011fildir. Unutulmu\u015f bir alt alan, d\u0131\u015f sa\u011flay\u0131c\u0131ya delege edilmi\u015f hizmet veya ba\u015far\u0131s\u0131z sertifika yenilemesi kullan\u0131c\u0131lar\u0131n siteye ula\u015fmas\u0131n\u0131 engelleyebilir.<\/p>\n

\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. HSTS preload nedir?<\/a><\/li>\n
  2. Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/a><\/li>\n
  3. Avantaj\u0131 ve kullan\u0131m ko\u015fullar\u0131<\/a><\/li>\n
  4. Ba\u015fvuru \u00f6ncesi ad\u0131mlar<\/a><\/li>\n
  5. \u0130leri teknik kontroller<\/a><\/li>\n
  6. Riskler ve kald\u0131rma<\/a><\/li>\n
  7. AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/a><\/li>\n
  8. \u0130lgili AIOWS yaz\u0131lar\u0131<\/a><\/li>\n
  9. Sonu\u00e7 ve \u00f6nerilen yol<\/a><\/li>\n
  10. Resm\u00ee kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n

    HSTS preload nedir?<\/h2>\n

    Normal HSTS politikas\u0131, taray\u0131c\u0131 ge\u00e7erli HTTPS yan\u0131t\u0131n\u0131 g\u00f6rd\u00fckten sonra kaydedilir. Preload listesinde ise alan daha ilk ba\u011flant\u0131dan \u00f6nce HTTPS olarak bilinir. Ba\u015fvuru i\u00e7in uzun max-age<\/code>, includeSubDomains<\/code> ve preload<\/code> y\u00f6nergesi gerekir.<\/p>\n

    Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/h2>\n

    \u015eirket ana WordPress sitesini preload listesine ekler; ancak legacy.example.com<\/code> d\u0131\u015f bir sa\u011flay\u0131c\u0131da yaln\u0131z HTTP ile \u00e7al\u0131\u015fmaktad\u0131r. includeSubDomains<\/code> nedeniyle taray\u0131c\u0131 bu hizmete HTTPS \u00fczerinden ba\u011flan\u0131r ve ba\u011flant\u0131 ba\u015far\u0131s\u0131z olur.<\/p>\n

    Alan daha sonra listeden \u00e7\u0131kar\u0131lsa bile g\u00fcncellemenin taray\u0131c\u0131 s\u00fcr\u00fcmlerine ula\u015fmas\u0131 zaman al\u0131r. Bu s\u00fcre boyunca sunucuda yap\u0131lan geri d\u00f6n\u00fc\u015f b\u00fct\u00fcn kullan\u0131c\u0131lar\u0131 hemen kurtarmaz.<\/p>\n

    Avantaj\u0131 ve kullan\u0131m ko\u015fullar\u0131<\/h2>\n

    Preload, ilk HTTP iste\u011finin d\u00fc\u015f\u00fcrme veya y\u00f6nlendirme sald\u0131r\u0131s\u0131na a\u00e7\u0131k olmas\u0131n\u0131 \u00f6nler. Fakat bu kazan\u0131m, alan ad\u0131n\u0131n tamam\u0131nda olgun HTTPS y\u00f6netimi gerektirir. B\u00fct\u00fcn mevcut ve gelecekteki alt alanlar\u0131n HTTPS sunaca\u011f\u0131ndan emin de\u011filseniz normal HSTS ile kalmak daha g\u00fcvenlidir.<\/p>\n

    Ba\u015fvuru \u00f6ncesi ad\u0131mlar<\/h2>\n
      \n
    1. DNS kay\u0131tlar\u0131n\u0131, delege edilmi\u015f alt alanlar\u0131 ve kullan\u0131lmayan eski hostlar\u0131 envantere al\u0131n.<\/li>\n
    2. Her hostta ge\u00e7erli sertifika ve otomatik yenilemeyi do\u011frulay\u0131n.<\/li>\n
    3. HSTS’yi preload olmadan uzun s\u00fcre i\u015fletip yenileme d\u00f6nemini g\u00f6zlemleyin.<\/li>\n
    4. includeSubDomains<\/code> kapsam\u0131n\u0131 ilgili i\u015f birimleri ve altyap\u0131 ekipleriyle onaylay\u0131n.<\/li>\n
    5. Preload uygunluk testini \u00e7al\u0131\u015ft\u0131r\u0131n ve kald\u0131rma plan\u0131n\u0131 belgeleyin.<\/li>\n
    6. Ba\u015fvurunun sorumlusunu ve yeni DNS kayd\u0131 a\u00e7ma politikas\u0131n\u0131 belirleyin.<\/li>\n<\/ol>\n

      \u0130leri teknik kontroller<\/h2>\n

      DNS ge\u00e7mi\u015fini, wildcard ve delege edilmi\u015f zone’lar\u0131, \u00fc\u00e7\u00fcnc\u00fc taraf SaaS hostlar\u0131n\u0131 ve afet kurtarma alanlar\u0131n\u0131 inceleyin. Her alt alanda sertifika kapsam\u0131n\u0131, IPv4\/IPv6 ba\u011flant\u0131s\u0131n\u0131 ve otomatik yenilemeyi s\u0131nay\u0131n. Preload durumunu temsil\u00ee taray\u0131c\u0131 listelerinde takip edin.<\/p>\n

      Yeni alt alan olu\u015fturma s\u00fcrecine HTTPS kurulumunu ve sertifika yenilemesinden sorumlu ekibin a\u00e7\u0131k\u00e7a belirlenmesini ekleyin. Preload karar\u0131 yaln\u0131z WordPress ekibinin de\u011fil, alan ad\u0131n\u0131 kullanan b\u00fct\u00fcn ekiplerin sorumlulu\u011fudur.<\/p>\n

      Riskler ve kald\u0131rma<\/h2>\n

      Preload, bilinmeyen veya gelecekte a\u00e7\u0131lacak alt alanlar\u0131 da etkiler. D\u0131\u015f sa\u011flay\u0131c\u0131 s\u00f6zle\u015fmesi sona ererse veya sertifika yenilemesi bozulursa HTTP’ye ge\u00e7ici d\u00f6n\u00fc\u015f m\u00fcmk\u00fcn de\u011fildir. Kald\u0131rma talebi verilebilir; ancak liste ve istemci g\u00fcncellemeleri anl\u0131k de\u011fildir.<\/p>\n

      \n

      AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/p>\n

      AIOWS SSL Y\u00f6neticisi<\/h2>\n

      Preload de\u011ferlendirmesinde AIOWS SSL Y\u00f6neticisi, ana WordPress sitesinin HTTPS ve desteklenen HSTS ayarlar\u0131 bak\u0131m\u0131ndan haz\u0131r olup olmad\u0131\u011f\u0131n\u0131 incelemeye yard\u0131mc\u0131 olur.<\/p>\n

      Preload karar\u0131 yaln\u0131z WordPress ayarlar\u0131na dayanamaz. AIOWS b\u00fct\u00fcn DNS alanlar\u0131n\u0131, d\u0131\u015f sa\u011flay\u0131c\u0131 s\u00f6zle\u015fmelerini veya taray\u0131c\u0131 preload listelerini y\u00f6netmez. Alt alan envanteri, sertifika yenilemesi ve her hizmetten sorumlu ekip ayr\u0131 ayr\u0131 do\u011frulanmal\u0131d\u0131r.<\/p>\n

      WordPress taraf\u0131nda belirsiz HTTPS, y\u00f6nlendirme veya sertifika sorunu varsa preload ba\u015fvurusunu erteleyin. \u00d6nce normal HSTS’yi g\u00fcvenle i\u015fletin; ba\u015fvuruyu ancak bir ekip alan\u0131n tamam\u0131n\u0131 uzun vadede i\u015fletme sorumlulu\u011funu a\u00e7\u0131k\u00e7a \u00fcstlendi\u011finde yap\u0131n.<\/p>\n

      AIOWS SSL Y\u00f6neticisi’ni inceleyin<\/a>AIOWS planlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n<\/a><\/p>\n<\/section>\n

      \u0130lgili AIOWS yaz\u0131lar\u0131<\/h2>\n