http > https, 2021 > 2022 in docs

2025-12-06 04:31:29 +00:00 · 2022-04-14 23:06:01 +00:00
parent 639efbd214
commit ec2176f733
23 changed files with 43 additions and 43 deletions
--- a/docs/man-xlate/nmap-man-de.xml
+++ b/docs/man-xlate/nmap-man-de.xml
@@ -3186,7 +3186,7 @@ IP-Adressen angeben.</para>
 <para>Wenn Sie die Optionen in den gesendeten und empfangenen Paketen 
 sehen möchten, geben Sie <option>--packet-trace</option> an. Mehr 
 Informationen und Beispiele zum Einsatz von IP-Optionen mit Nmap finden 
-Sie unter <ulink url="http://seclists.org/nmap-dev/2006/q3/0052.html"/>.
+Sie unter <ulink url="https://seclists.org/nmap-dev/2006/q3/0052.html"/>.
 </para>

      </listitem>
@@ -4298,9 +4298,9 @@ sollten Sie zuerst auf die neueste Version aktualisieren, die unter
 <ulink url="https://nmap.org"/> verfügbar ist. Wenn das Problem anhält, 
 versuchen Sie herauszufinden, ob es bereits erkannt und bearbeitet 
 wurde. Suchen Sie nach der Fehlermeldung auf unserer Suchseite unter 
-<ulink url="http://insecure.org/search.html"/> oder bei Google. Stöbern 
+<ulink url="https://insecure.org/search.html"/> oder bei Google. Stöbern 
 Sie in den <citetitle>nmap-dev</citetitle>-Archiven unter 
-<ulink url="http://seclists.org/" />.<indexterm><primary><citetitle>nmap-dev</citetitle> Mailingliste</primary></indexterm> 
+<ulink url="https://seclists.org/" />.<indexterm><primary><citetitle>nmap-dev</citetitle> Mailingliste</primary></indexterm> 
 Lesen Sie auch diese Manpage vollständig. Wenn Sie keine Lösung finden, 
 schicken Sie einen Fehlerbericht per E-Mail an 
 <email>dev@nmap.org</email>. Beschreiben Sie darin bitte alles, 
@@ -4325,7 +4325,7 @@ geschickt werden.</para>
    <title>Autor</title>
    <para>Fyodor 
    <email>fyodor@nmap.org</email>
-    (<ulink url="http://insecure.org" />)
+    (<ulink url="https://insecure.org" />)
    </para>

    <para>Über die Jahre haben hunderte von Menschen wertvolle Beiträge 
--- a/docs/man-xlate/nmap-man-es.xml
+++ b/docs/man-xlate/nmap-man-es.xml
@@ -3553,7 +3553,7 @@ medida que se incrementa el nivel de depuraci
    investiga para determinar si la causa ya ha sido descubierta y
    solucionada. Busca en Google el mensaje de error o navega en los
    archivos de Nmap-dev en <ulink
-    url="http://seclists.org/"/>. Tambi<62>n deber<65>as leer este manual
+    url="https://seclists.org/"/>. Tambi<62>n deber<65>as leer este manual
    completo. Si esto no te ayuda, env<6E>a un informe de error en ingl<67>s
    a <email>dev@nmap.org</email>.  Por favor, incluya todo
    lo que haya visto del problema, as<61> como qu<71> versi<73>n de Nmap
--- a/docs/man-xlate/nmap-man-fr.xml
+++ b/docs/man-xlate/nmap-man-fr.xml
@@ -1522,7 +1522,7 @@ le temps suppl
            <para>Si vous souhaitez voir les options dans les paquets envoy<6F>s et  
      recus, sp<73>cifiez <option>--packet-trace</option>.  Pour plus 
      d'information et d'exemples de l'utilisation des options IP avec Nmap, voir 
-      <ulink url="http://seclists.org/nmap-dev/2006/q3/0052.html" />.</para>
+      <ulink url="https://seclists.org/nmap-dev/2006/q3/0052.html" />.</para>
          </listitem>
        </varlistentry>
        <varlistentry>
@@ -2273,7 +2273,7 @@ le temps suppl
 						disponible sur <ulink url="https://nmap.org/" />. Si le probl<62>me persiste,
 						faites quelques recherches afin de d<>terminer s'il a d<>j<EFBFBD> <20>t<EFBFBD> remarqu<71> et
 						signal<61>. Essayez pour cela de mettre l'erreur en argument sur Google
-						ou parcourez les archives de Nmap-dev sur <ulink url="http://seclists.org/" />. Lisez ce manuel en entier quoiqu'il en
+						ou parcourez les archives de Nmap-dev sur <ulink url="https://seclists.org/" />. Lisez ce manuel en entier quoiqu'il en
 						soit. Si rien ne semble fonctionner, envoyez un rapport de bogue <20>
 						<email>dev@nmap.org</email>. Veillez <20> inclure tout ce que vous avez
 						appris au sujet de ce bogue ainsi que la version de Nmap concern<72>e
--- a/docs/man-xlate/nmap-man-hr.xml
+++ b/docs/man-xlate/nmap-man-hr.xml
@@ -2408,7 +2408,7 @@ samoobjašnjavajuće, ali poruke postaju sve čudnije što je nivo debugiranja v
    dostupnu na
    <ulink url="https://nmap.org/"></ulink>. Ukoliko je problem i dalje tu, istražite da li je već
    otkriven i prijavljen. Pokušajte "zaguglati" poruku o grešci ili otiđite na Nmap-dev arhive na
-    <ulink url="http://seclists.org/"></ulink>. Također pročitajte i kompletan manual. Ukoliko ništa od toga ne
+    <ulink url="https://seclists.org/"></ulink>. Također pročitajte i kompletan manual. Ukoliko ništa od toga ne
    pomogne, pošaljite izvještaj o grešci na <email>dev@nmap.org</email>. Molim Vas napišite sve što ste do
    tad otkrili o problemu, te koju verziju Nmap- imate i koju verziju OS-a imate. Izvještaji o prijavljenim
    problemima i upiti o korištenju Nmap-a koji su poslani na dev@nmap.org imaju više šansi da budu
--- a/docs/man-xlate/nmap-man-hu.xml
+++ b/docs/man-xlate/nmap-man-hu.xml
@@ -2721,7 +2721,7 @@ mértékben támogatja ezt a paramétert.</para>
      lévő beállításokat, adja meg a <option>--packet-trace</option> paramétert. 
      Ha további információkra és példákra kíváncsi az Nmap programban használható 
      IP paraméterekkel kapcsolatban, látogasson el a 
-      <ulink url="http://seclists.org/nmap-dev/2006/q3/0052.html"></ulink> címre.
+      <ulink url="https://seclists.org/nmap-dev/2006/q3/0052.html"></ulink> címre.
      </para>

      </listitem>
@@ -3635,7 +3635,7 @@ kapuk csak egy számként jelennek meg, ha túl sok van belőlük.
    változatot a <ulink url="https://nmap.org"></ulink> címről. Ha a probléma továbbra 
    is fennáll, nézzen utána, hogy felfedezték-e már mások is. Keressen rá a 
    Google-ban a hibaüzenetre vagy böngéssze át az Nmap fejlesztői listát a 
-    <ulink url="http://seclists.org/"></ulink> címen. Olvassa végig ezt a leírást 
+    <ulink url="https://seclists.org/"></ulink> címen. Olvassa végig ezt a leírást 
    is. Ha nem talál semmit, küldjön egy hibajelentést az <email>dev@nmap.org</email> 
    címre. Írjon le mindent, amit a hibával kapcsolatban tapasztalt. Adja meg 
    pontosan a használt Nmap változatot és a futtató operációs rendszer változatát 
@@ -3653,7 +3653,7 @@ kapuk csak egy számként jelennek meg, ha túl sok van belőlük.
    <title>Szerző</title>
    <para>Fyodor 
    <email>fyodor@nmap.org</email>
-    (<ulink url="http://insecure.org"></ulink>)
+    (<ulink url="https://insecure.org"></ulink>)
    </para>

    <para>Az évek során emberek százai járultak hozzá értékes munkájukkal az Nmap 
--- a/docs/man-xlate/nmap-man-id.xml
+++ b/docs/man-xlate/nmap-man-id.xml
@@ -2917,7 +2917,7 @@ mendukung opsi secara penuh, demikian pula scan UDP.</para>
      <para>Jika anda ingin melihat opsi dalam paket yang dikirim dan diterima,
      berikan <option>--packet-trace</option>.  Informasi dan contoh lebih lanjut
      tentang penggunaan opsi IP dengan Nmap, dapat dilihat di
-      <ulink url="http://seclists.org/nmap-dev/2006/q3/0052.html"/>.
+      <ulink url="https://seclists.org/nmap-dev/2006/q3/0052.html"/>.
      </para>

      </listitem>
@@ -3940,8 +3940,8 @@ banyaknya permintaan.  Berikan <option>--open</option> untuk hanya melihat port
    Nmap tidak berlaku sesuai yang anda harapkan, pertama upgrade ke versi terakhir
    yang tersedia dari <ulink url="https://nmap.org"/>.  Jika masalah masih tetap,
    lakukan riset untuk menentukan apakah ia telah ditemukan dan diselesaikan.
-    Cobalah mencari pesan kesalahan pada halaman pencarian kami <ulink url="http://insecure.org/search.html"/> atau di Google.  Juga cobalah
-    membrowsing arsip <citetitle>nmap-dev</citetitle> di <ulink url="http://seclists.org/"/>.<indexterm significance="normal"><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
+    Cobalah mencari pesan kesalahan pada halaman pencarian kami <ulink url="https://insecure.org/search.html"/> atau di Google.  Juga cobalah
+    membrowsing arsip <citetitle>nmap-dev</citetitle> di <ulink url="https://seclists.org/"/>.<indexterm significance="normal"><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
    Bacalah juga halaman manual ini dengan baik.
    Jika masih belum selesai juga, kirimkan laporan bug ke
    <email>dev@nmap.org</email>.  Mohon sertakan semua yang
@@ -3962,7 +3962,7 @@ banyaknya permintaan.  Berikan <option>--open</option> untuk hanya melihat port
    <title>Penulis</title>
    <para>Fyodor 
    <email>fyodor@nmap.org</email>
-    (<ulink url="http://insecure.org"/>)
+    (<ulink url="https://insecure.org"/>)
    </para>

    <para>Selama ini, ratusan orang telah memberikan kontribusi berharga ke Nmap.
--- a/docs/man-xlate/nmap-man-it.xml
+++ b/docs/man-xlate/nmap-man-it.xml
@@ -4543,9 +4543,9 @@ SEE THE MAN PAGE (https://nmap.org/book/man.html) FOR MORE OPTIONS AND EXAMPLES
      versione disponibile su <ulink url="https://nmap.org/" />. Se il problema
      persiste effettua qualche ricerca per determinare se il problema è stato
      già scoperto e segnalato. Prova a cercare sulla nostra pagina di ricerca
-      <ulink url="http://insecure.org/search.html" /> o su Google il messaggio
+      <ulink url="https://insecure.org/search.html" /> o su Google il messaggio
      di errore o ancora a sfogliare l'archivio Nmap-dev all'indirizzo <ulink
-      url="http://seclists.org/" />. Leggi inoltre tutta questa pagina di
+      url="https://seclists.org/" />. Leggi inoltre tutta questa pagina di
      manuale. Se nulla di questo riguarda il tuo caso, manda un bug report a
      <email>dev@nmap.org</email>. Accertati di includere ogni cosa che sei
      riuscito a sapere sul problema, la versione di Nmap che hai installato e
--- a/docs/man-xlate/nmap-man-ja.xml
+++ b/docs/man-xlate/nmap-man-ja.xml
@@ -1346,7 +1346,7 @@ rttvar: 14987 to: 100000</computeroutput>。こうした行の内容が理解で
  <refsect1 id="man-bugs">
    <title>バグ</title>

-    <para>Nmapも作者と同様に完全ではない。それでもNmapのほうは、ユーザによるバグの報告やパッチの作成のおかげで、よりよいものにしてゆくことができる。Nmapを使っていて、思い通りに動かない場合は、まず<ulink url="https://nmap.org/"/>から入手できる最新のバージョンにアップグレードしてみる。問題が続くようなら、すでに発見・対処が行われた問題かどうかを調査して確かめる。エラーメッセージをGoogle検索したり、<ulink url="http://seclists.org/"/>でNmap-devアーカイブを閲覧したりしてみる。このmanページも全体に目を通した方がよい。それでもどうにもならない場合は、バグレポートを<email>dev@nmap.org</email>宛てにメールで送ること。メールには、使用しているNmapのバージョンと、Nmapを実行しているOSの名前とバージョンなどの情報だけでなく、問題に関して分かったことは何でも書いていただきたい。問題の報告やNmapの使い方についての質問などは、dev@nmap.org宛てに送るほうが、筆者宛てに直接送るよりも返事がある可能性ははるかに高い。 </para>
+    <para>Nmapも作者と同様に完全ではない。それでもNmapのほうは、ユーザによるバグの報告やパッチの作成のおかげで、よりよいものにしてゆくことができる。Nmapを使っていて、思い通りに動かない場合は、まず<ulink url="https://nmap.org/"/>から入手できる最新のバージョンにアップグレードしてみる。問題が続くようなら、すでに発見・対処が行われた問題かどうかを調査して確かめる。エラーメッセージをGoogle検索したり、<ulink url="https://seclists.org/"/>でNmap-devアーカイブを閲覧したりしてみる。このmanページも全体に目を通した方がよい。それでもどうにもならない場合は、バグレポートを<email>dev@nmap.org</email>宛てにメールで送ること。メールには、使用しているNmapのバージョンと、Nmapを実行しているOSの名前とバージョンなどの情報だけでなく、問題に関して分かったことは何でも書いていただきたい。問題の報告やNmapの使い方についての質問などは、dev@nmap.org宛てに送るほうが、筆者宛てに直接送るよりも返事がある可能性ははるかに高い。 </para>

    <para>またバグレポートより、バグを修正するためのコードパッチのほうが歓迎される。ユーザ自身のコード変更によるパッチファイルの作成方法についての基本的な注意事項は<ulink url="https://nmap.org/data/HACKING"/> で参照できる。パッチは、nmap-dev宛てに送る(推奨)か、筆者Fyodorまで直接送っていただきたい。</para>
  </refsect1>
--- a/docs/man-xlate/nmap-man-pl.xml
+++ b/docs/man-xlate/nmap-man-pl.xml
@@ -3048,7 +3048,7 @@ podobnie jak i UDP.</para>
    wyst&#281;puje, wykonaj troch&#281; test&#243;w dla okre&#347;lenia czy podobny problem nie 
    zosta&#322; ju&#380; wykryty i oznaczony. Spr&#243;buj poszuka&#263; Googlem komunikatu
    b&#322;&#281;du lub poprzegl&#261;daj archiwa listy dyskusyjnej Nmap-dev pod adresem
-    <ulink url="http://seclists.org/"/>. Przeczytaj r&#243;wnie&#380; ca&#322;a dokumentacj&#281;.
+    <ulink url="https://seclists.org/"/>. Przeczytaj r&#243;wnie&#380; ca&#322;a dokumentacj&#281;.
    Je&#347;li nic nie pomo&#380;e, wy&#347;lij raport opisuj&#261;cy b&#322;&#261;d po angielsku na adres
    <email>dev@nmap.org</email>. Prosz&#281; do&#322;&#261;cz wszystko co uda&#322;o Ci
    si&#281; ustali&#263; na temat tego problemu, jak r&#243;wnie&#380; informacj&#281; o u&#380;ywanej 
--- a/docs/man-xlate/nmap-man-pt_BR.xml
+++ b/docs/man-xlate/nmap-man-pt_BR.xml
@@ -3765,7 +3765,7 @@ EXAMPLES:
      url="https://nmap.org/" />. Se o problema persistir, pesquise um
      pouco para determinar se o problema já foi descoberto e encaminhado.
      Tente procurar no Google pela mensagem de erro ou navegar nos arquivos
-      da Nmap-dev em <ulink url="http://seclists.org/" />. Se não encontrar
+      da Nmap-dev em <ulink url="https://seclists.org/" />. Se não encontrar
      nada, envie uma mensagem com um relatório do erro para
      <email>dev@nmap.org</email>. Por favor, inclua tudo o que
      souber sobre o problema, bem como a versão do Nmap que você está
@@ -3782,7 +3782,7 @@ EXAMPLES:
      <title>Autor</title>

      <para>Fyodor <email>fyodor@nmap.org</email> (<ulink
-      url="http://insecure.org" />)</para>
+      url="https://insecure.org" />)</para>

      <para>Centenas de pessoas fizeram contribuições valiosas para o Nmap ao
      longo dos anos. Isso está detalhado no arquivo <filename
--- a/docs/man-xlate/nmap-man-pt_PT.xml
+++ b/docs/man-xlate/nmap-man-pt_PT.xml
@@ -3080,7 +3080,7 @@ EXEMPLOS:
      url="https://nmap.org/" />. Se o problema persistir,
      pesquise um pouco para determinar se o problema j<> foi descoberto e
      encaminhado. Tente procurar no Google pela mensagem de erro ou navegar
-      nos arquivos da Nmap-dev em <ulink url="http://seclists.org/" />. Se n<>o
+      nos arquivos da Nmap-dev em <ulink url="https://seclists.org/" />. Se n<>o
      encontrar nada envie uma mensagem com um relat<61>rio do erro para
      <email>dev@nmap.org</email>. Por favor inclua tudo o que
      souber sobre o problema bem como a vers<72>o do Nmap que est<73>
--- a/docs/man-xlate/nmap-man-ro.xml
+++ b/docs/man-xlate/nmap-man-ro.xml
@@ -2943,7 +2943,7 @@
      persista, faceti munca de cercetare pentru a vedea daca problema a fost
      descoperita si discutata. Incercati cautarea in Google a mesajului de
      eroare sau navigand prin arhivele Nmap-dev la
-      <ulink url="http://seclists.org/"></ulink>. Cititi acest manual in
+      <ulink url="https://seclists.org/"></ulink>. Cititi acest manual in
      intregime de asemenea. Daca nimic nu se rezolva, trimiteti un mail la
      <email>dev@nmap.org</email>. Va rog sa includeti tot ce ati
      aflat despre problema, precum si versiunea de Nmap pe care o folositi si
--- a/docs/man-xlate/nmap-man-ru.xml
+++ b/docs/man-xlate/nmap-man-ru.xml
@@ -2583,7 +2583,7 @@ Nmap по умолчанию, она включает распараллелив

      <para>Если вы хотите заданные опции в передаваемых и получаемых пакетах, задайте опцию 
      <option>--packet-trace</option>. Для большей информации и примеров использования IP опций с Nmap, смотрите
-      <ulink url="http://seclists.org/nmap-dev/2006/q3/0052.html"/>.
+      <ulink url="https://seclists.org/nmap-dev/2006/q3/0052.html"/>.
      </para>

      </listitem>
@@ -3463,8 +3463,8 @@ rttvar: 14987 to: 100000</computeroutput>. Если вы не понимаете
    <para>Как и ее автор, Nmap не идеальна. Но вы можете сделать ее лучше посылая нам отчеты об ошибках или даже 
    написав патч. Если Nmap ведет себя не так, как вы ожидаете, то для начала обновитесь до последней версии с 
    <ulink url="https://nmap.org"/>. Если проблема останется, то выясните, не была ли эта проблема уже обнаружена кем-то. 
-    Попробуйте поискать сообщения об ошибках на нашей странице поиска <ulink url="http://insecure.org/search.html"/> 
-    или в Google. Также попробуйте просмотреть <citetitle>nmap-dev</citetitle> архивы на <ulink url="http://seclists.org/"/>.<indexterm significance="normal"><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
+    Попробуйте поискать сообщения об ошибках на нашей странице поиска <ulink url="https://insecure.org/search.html"/> 
+    или в Google. Также попробуйте просмотреть <citetitle>nmap-dev</citetitle> архивы на <ulink url="https://seclists.org/"/>.<indexterm significance="normal"><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
    Также прочитайте полностью страницу руководства. Если ничего не помогло, отправьте сообщение об ошибке на 
    <email>dev@nmap.org</email>. Пожалуйста, включите всю известную вам информацию об ошибке, какую версию 
    Nmap вы используете, и на какой операционной системы вы запускаете Nmap. Сообщения о проблемах и вопросы по 
@@ -3481,7 +3481,7 @@ rttvar: 14987 to: 100000</computeroutput>. Если вы не понимаете
    <title>Автор</title>
    <para>Fyodor 
    <email>fyodor@nmap.org</email>
-    (<ulink url="http://insecure.org"/>)
+    (<ulink url="https://insecure.org"/>)
    </para>

    <para>На протяжении многих лет сотни людей внесли ценный вклад в разработку Nmap. Все изменения и улучшения 
--- a/docs/man-xlate/nmap-man-sk.xml
+++ b/docs/man-xlate/nmap-man-sk.xml
@@ -2804,7 +2804,7 @@ Niektore riadku su samovysvetlujuce, no zvysovanim stupna debugovania sa straca
 	<ulink url="https://nmap.org/"/>.  Ak problem pretrvava,
 	preskumajte, ci uz nebol objaveny a adresovany. Vyskusajte pouzit google
 	s vyrazom chybovej spravy alebo prehladajte archivy Nmap-dev na adrese
-    <ulink url="http://seclists.org/"/>.  Precitajte si aj tento plny manual.
+    <ulink url="https://seclists.org/"/>.  Precitajte si aj tento plny manual.
 	Ak nenajdete nic podobne, poslite mail o bugu na adresu 
    <email>dev@nmap.org</email>.  Zahrnte vsetko, co ste sa dozvedeli
 	o probleme spolu s verziou Nmapu a operacnym systemom. Spravy o problemoch
--- a/docs/man-xlate/nmap-man-zh.xml
+++ b/docs/man-xlate/nmap-man-zh.xml
@@ -2311,7 +2311,7 @@ rttvar: 14987 to: 100000</computeroutput>。如果对某行输出不明白，
    <para>和作者一样，Nmap也不是完美的，但可以通过发送Bug报告甚至编写
    补丁使其更加完善。如果Nmap不能满足要求，首先从<ulink url="https://nmap.org/"/>
    升级最新版本。如果总问题仍然存在，需要进行调查以确定问题是否
-    已经被解决。在<ulink url="http://seclists.org/"/>尝试搜索出错消息或
+    已经被解决。在<ulink url="https://seclists.org/"/>尝试搜索出错消息或
    浏览Nmap-dev档案，以及仔细阅读使用手册。如果问题还是不能解决，发送
    Bug报告至<email>dev@nmap.org</email>。在报告中包含所有
    有关问题的信息，以及所使用的Nmap版本、操作系统版本。问题报告以及
--- a/docs/nmap-install.xml
+++ b/docs/nmap-install.xml
@@ -146,7 +146,7 @@ sub 2048g/D3C2241C 2005-04-24

 pub 1024D/6B9355D0 2005-04-24
    Key fingerprint = 436D 66AB 9A79 8425 FDA0 E3F8 01AF 9F03 6B93 55D0
-uid                Nmap Project Signing Key (http://insecure.org/)
+uid                Nmap Project Signing Key (https://insecure.org/)
 sub 2048g/A50A6A94 2005-04-24
 </screen></example>

@@ -481,7 +481,7 @@ If you make code changes to fix the problem, please send a patch
 <varlistentry><term>Ask Google and other Internet resources</term>
 <listitem><para>Try searching for the exact error message on Google or other search engines.  You might also want to browse recent activity on the Nmap development
 (<citetitle>nmap-dev</citetitle>)<indexterm><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
-list&mdash;archives and a search interface are available at <ulink url="http://seclists.org" />.</para></listitem></varlistentry>
+list&mdash;archives and a search interface are available at <ulink url="https://seclists.org" />.</para></listitem></varlistentry>

 <varlistentry><term>Ask <citetitle>nmap-dev</citetitle></term>
 <listitem><para>If none of your research leads to a solution, try
--- a/docs/refguide.xml
+++ b/docs/refguide.xml
@@ -3503,7 +3503,7 @@ work properly.</para>
      <para>If you wish to see the options in packets sent and
      received, specify <option>--packet-trace</option>.  For more
      information and examples of using IP options with Nmap, see
-      <ulink url="http://seclists.org/nmap-dev/2006/q3/52"/>.
+      <ulink url="https://seclists.org/nmap-dev/2006/q3/52"/>.
      </para>

      </listitem>
--- a/docs/scripting.xml
+++ b/docs/scripting.xml
@@ -56,7 +56,7 @@
          <para>When a new vulnerability is discovered, you often want
       to scan your networks quickly to identify vulnerable systems
       before the bad guys do.  While Nmap isn't a
-       comprehensive <ulink role="hidepdf" url="http://sectools.org/vuln-scanners.html">vulnerability scanner</ulink>,
+       comprehensive <ulink role="hidepdf" url="https://sectools.org/vuln-scanners.html">vulnerability scanner</ulink>,
       NSE is powerful enough to handle even demanding vulnerability
       checks. When the Heartbleed bug affected hundreds of thousands of
       systems worldwide, Nmap's developers responded with the
--- a/docs/zenmap.xml
+++ b/docs/zenmap.xml
@@ -132,7 +132,7 @@
    latest version available from <ulink url="https://nmap.org"/>.  If
    the problem persists, do some research to determine whether it has already
    been discovered and addressed.  Try Googling the error message or browsing
-    the <citetitle>nmap-dev</citetitle> archives at <ulink url="http://seclists.org/" />.
+    the <citetitle>nmap-dev</citetitle> archives at <ulink url="https://seclists.org/" />.
    Read this
    full manual page as well.  If nothing comes of this, mail a bug report to
    <email>dev@nmap.org</email>.  Please include everything you have
@@ -166,7 +166,7 @@
      <title>Nmap</title>
      <para>Fyodor 
      <email>fyodor@nmap.org</email>
-      (<ulink url="http://insecure.org" />)
+      (<ulink url="https://insecure.org" />)
      </para>

      <para>Hundreds of people have made valuable contributions to Nmap
--- a/ncat/docs/ncat.xml
+++ b/ncat/docs/ncat.xml
@@ -1084,7 +1084,7 @@
    do some research to determine whether it has already been
    discovered and addressed.  Try Googling the error message or
    browsing the <citetitle>nmap-dev</citetitle> archives at <ulink
-    url="http://seclists.org/" />.
+    url="https://seclists.org/" />.
    <indexterm><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
    Read this full manual page as
    well.  If nothing comes of this, mail a bug report to
@@ -1134,7 +1134,7 @@
  <title>Ncat Copyright and Licensing</title>
  <indexterm><primary>copyright</primary></indexterm>

-  <para>Ncat is (C) 2005&ndash;2021 Nmap Software LLC. It is distributed
+  <para>Ncat is (C) 2005&ndash;2022 Nmap Software LLC. It is distributed
  as free and open source software under the same license terms as our
  Nmap software.  Precise terms and further details are available
  <man>from <ulink url="https://nmap.org/man/man-legal.html"/>.</man>
@@ -1144,7 +1144,7 @@
 <refsect2 id="ncat-man-copyright">
  <title>Creative Commons License for this Ncat Guide</title>
  <para>This <citetitle>Ncat Reference Guide</citetitle> is (C)
-  2005&ndash;2021 Nmap Software LLC. It is
+  2005&ndash;2022 Nmap Software LLC. It is
   hereby placed under version 3.0 of the <ulink
   url="http://creativecommons.org/licenses/by/3.0/">Creative Commons
   Attribution License</ulink>.  This allows you redistribute and modify
--- a/ncat/docs/ncatguide.xml
+++ b/ncat/docs/ncatguide.xml
@@ -1589,7 +1589,7 @@ host1$ <userinput>ncat --send-only host2 &lt; log.txt</userinput>
    <title>Unwrap SSL</title>

    <!-- This trick was suggested by Brandon Enright.
-         http://seclists.org/nmap-dev/2009/q1/379 -->
+         https://seclists.org/nmap-dev/2009/q1/379 -->
    <para>
    Suppose you need to connect to an
    IMAP<indexterm><primary>IMAP</primary></indexterm> server that
@@ -1620,7 +1620,7 @@ host1$ <userinput>ncat --send-only host2 &lt; log.txt</userinput>
    <title>Use SSH Through an Ncat Tunnel</title>

    <!-- This trick was suggested by Greg Darke.
-         http://seclists.org/nmap-dev/2009/q1/403 -->
+         https://seclists.org/nmap-dev/2009/q1/403 -->
    <para>
    With Ncat and OpenSSH<indexterm><primary>OpenSSH</primary></indexterm>
    you can SSH to a host behind a NAT<indexterm><primary>network address translation</primary></indexterm>
--- a/ndiff/docs/ndiff.xml
+++ b/ndiff/docs/ndiff.xml
@@ -387,7 +387,7 @@ ln -sf scan-$date.xml scan-prev.xml
    in Perl and C++, but the summer ended shortly after it was decided
    to rewrite the program in Python for the sake of Windows (and
    Zenmap) compatibility. This Python version was written by David
-    Fifield.  James Levine <ulink url="http://seclists.org/nmap-hackers/2000/315">released</ulink> a Perl script named Ndiff with
+    Fifield.  James Levine <ulink url="https://seclists.org/nmap-hackers/2000/315">released</ulink> a Perl script named Ndiff with
    similar functionality in 2000.
    </para>
  </refsect1>
--- a/nping/docs/nping-man.xml
+++ b/nping/docs/nping-man.xml
@@ -2145,7 +2145,7 @@ SENT (4.0330s) TCP 192.168.0.21 &gt; 3.3.3.3:139
          <para>
           For more information and examples of using IP options with Nping,
           see the mailing list post at
-           <ulink url="http://seclists.org/nmap-dev/2006/q3/0052.html"/>.
+           <ulink url="https://seclists.org/nmap-dev/2006/q3/0052.html"/>.
          </para>
        </listitem>
      </varlistentry>
@@ -3552,7 +3552,7 @@ NSOCK (1.0000s) Callback: TIMER SUCCESS for EID 12; tcpconnect_event_handler<con

    <para>Luis MartinGarcia <email>luis.mgarc@gmail.com</email> (<ulink url="http://www.luismg.com" />)</para>

-    <para>Fyodor <email>fyodor@nmap.org</email> (<ulink url="http://insecure.org" />)</para>
+    <para>Fyodor <email>fyodor@nmap.org</email> (<ulink url="https://insecure.org" />)</para>

  </refsect1>