6 files changed, 12 insertions, 12 deletions
diff --git a/doc/getaddrinfo.html b/doc/getaddrinfo.html
index d0fd1ac..a6ea981 100644
--- a/doc/getaddrinfo.html
+++ b/doc/getaddrinfo.html
@@ -21,7 +21,7 @@
 <p>
  The standard C library provides an API to perform name
 resolution:
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/getaddrinfo.html">getaddrinfo()</a>,
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/getaddrinfo.html">getaddrinfo()</a>,
 formerly <tt>gethostbyname()</tt>. However, for DNS resolution as well as
 implementation in the libc, this interface is very impractical, to the point of
 being unusable. Here are a few reasons why.
@@ -31,8 +31,8 @@ being unusable. Here are a few reasons why.
 
 <p>
  I explained this point in a message to the
-<a href="http://busybox.net/">Busybox</a> mailing-list. You can
-<a href="http://lists.busybox.net/pipermail/busybox/2012-July/078123.html">read
+<a href="https://busybox.net/">Busybox</a> mailing-list. You can
+<a href="https://lists.busybox.net/pipermail/busybox/2012-July/078123.html">read
 the post here</a>.
 (There is a mistake in that post about <tt>/etc/nsswitch.conf</tt> and
 <tt>/etc/host.conf</tt> syntax; the following two messages in the thread
diff --git a/doc/index.html b/doc/index.html
index 2eb5016..9fdc636 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -54,7 +54,7 @@ requirement if you link against the shared version of the skalibs library. </li>
 
 <p>
  s6-dns is free software. It is available under the
-<a href="http://opensource.org/licenses/ISC">ISC license</a>.
+<a href="https://opensource.org/licenses/ISC">ISC license</a>.
 </p>
 
 <h3> Download </h3>
@@ -165,17 +165,17 @@ relevant page.
  <li> <tt>s6-dns</tt> is discussed on the
 <a href="//skarnet.org/lists.html#skaware">skaware</a> mailing-list. </li>
  <li> It can also be discussed on the
-<a href="http://cr.yp.to/lists.html#dns">cr.yp.to dns mailing-list</a>. </li>
+<a href="https://cr.yp.to/lists.html#dns">cr.yp.to dns mailing-list</a>. </li>
 </ul>
 
 <h3> Similar work </h3>
 
 <ul>
- <li> <a href="http://www.isc.org/software/bind">BIND</a> is the most widely
+ <li> <a href="https://www.isc.org/software/bind">BIND</a> is the most widely
 used DNS software suite on the Internet. It's also arguably the most
-<a href="http://cr.yp.to/djbdns/blurb/unbind.html">buggy</a>,
+<a href="https://cr.yp.to/djbdns/blurb/unbind.html">buggy</a>,
 convoluted and impossible to understand. </li>
- <li> <a href="http://cr.yp.to/djbdns.html">djbdns</a> is DJB's DNS suite.
+ <li> <a href="https://cr.yp.to/djbdns.html">djbdns</a> is DJB's DNS suite.
 It works very well, but is unfortunately unmaintained by the author. s6-dns
 follows <a href="//skarnet.org/software/skalibs/djblegacy.html">the
 same design principles</a>. </li>
diff --git a/doc/libresolv.html b/doc/libresolv.html
index df24eee..ac5e027 100644
--- a/doc/libresolv.html
+++ b/doc/libresolv.html
@@ -34,7 +34,7 @@ Here are a few reasons why.
  The same people who wrote BIND wrote libresolv. That is the amount of
 trust you can place in libresolv. Ten years ago, the security status
 of libresolv looked like
-<a href="http://cr.yp.to/djbdns/res-disaster.html">this</a>. I am not
+<a href="https://cr.yp.to/djbdns/res-disaster.html">this</a>. I am not
 confident that is has improved: bugs in the software may have been
 fixed, but new ones will appear, and most importantly, the security
 management policy at ISC is still the same: security holes will be
diff --git a/doc/libs6dns/s6dns-engine.html b/doc/libs6dns/s6dns-engine.html
index 43fe621..5a24194 100644
--- a/doc/libs6dns/s6dns-engine.html
+++ b/doc/libs6dns/s6dns-engine.html
@@ -34,7 +34,7 @@ network, and getting answers.
 
 <p>
  <tt>s6dns_engine</tt> has been inspired by Dan J. Bernstein's
-<a href="http://cr.yp.to/djbdns/dns_transmit.html">dns_transmit</a>
+<a href="https://cr.yp.to/djbdns/dns_transmit.html">dns_transmit</a>
 library, but does not borrow any code from it. Unlike
 <tt>dns_transmit</tt>, <tt>s6dns_engine</tt> does not assume that
 network send operations are instant successes; <tt>s6dns_engine</tt>
diff --git a/doc/libs6dns/s6dns-resolve.html b/doc/libs6dns/s6dns-resolve.html
index 5d021aa..8dc6bef 100644
--- a/doc/libs6dns/s6dns-resolve.html
+++ b/doc/libs6dns/s6dns-resolve.html
@@ -92,7 +92,7 @@ The other prototypes can be found in the <tt>s6-dns/s6dns-resolve.h</tt> file.
 <p>
  Some <tt>errno</tt> codes reported by these functions do not have
 exactly the system meaning given by
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/strerror.html">strerror()</a>.
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/strerror.html">strerror()</a>.
 To get a user-friendly error message, use
 <tt>s6dns_constants_error_str(errno)</tt> instead. The <tt>s6dns_constants_error_str</tt>
 function is declared in the <tt>s6dns-constants.h</tt> header.
diff --git a/doc/skadns/skadnsd.html b/doc/skadns/skadnsd.html
index 6e6515c..c2d1736 100644
--- a/doc/skadns/skadnsd.html
+++ b/doc/skadns/skadnsd.html
@@ -83,7 +83,7 @@ that it requires support from the system administrator.
 skadnsd has no "standalone" mode: it is designed to work with a Unix
 domain superserver, like
 <a href="//skarnet.org/software/s6/s6-ipcserver.html">s6-ipcserver</a>.
-skadnsd follows the <a href="http://cr.yp.to/proto/ucspi.txt">UCSPI</a>
+skadnsd follows the <a href="https://cr.yp.to/proto/ucspi.txt">UCSPI</a>
 interface, it can be directly executed from the superserver.
 </p>