diff --git a/CHANGES.rst b/CHANGES.rst
index b0aa74d..d0eb1ec 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -157,7 +157,7 @@ Development:
 * #35: Drop support for Django 1.8, 1.9 and 1.10.
 * #40: Support Django 2.0.
 * #42: Support DISTKEY. Thanks to Benjy Weinberger.
-* Documentation: http://django-redshift-backend.rtfd.io/
+* Documentation: https://django-redshift-backend.rtfd.io/
 * Change LICENSE from 'BSD License' to 'Apache Software License'
 
 0.8.1 (2018-06-19)
@@ -196,7 +196,7 @@ Bug Fixes:
 
 Documentation:
 
-* Add documentation: http://django-redshift-backend.rtfd.io/
+* Add documentation: https://django-redshift-backend.rtfd.io/
 
 
 0.7 (2017-06-08)
diff --git a/django_redshift_backend/base.py b/django_redshift_backend/base.py
index df6cf2b..368f408 100644
--- a/django_redshift_backend/base.py
+++ b/django_redshift_backend/base.py
@@ -64,8 +64,8 @@ def last_insert_id(self, cursor, table_name, pk_name):
         retrieve MAX(pk) after insertion as a workaround.
 
         refs:
-        * http://stackoverflow.com/q/19428860
-        * http://stackoverflow.com/q/25638539
+        * https://stackoverflow.com/q/19428860
+        * https://stackoverflow.com/q/25638539
 
         How about ``return cursor.lastrowid`` that is implemented in
         django.db.backends.base.operations? Unfortunately, it doesn't
diff --git a/doc/dev.rst b/doc/dev.rst
index 0ff9f64..1e18832 100644
--- a/doc/dev.rst
+++ b/doc/dev.rst
@@ -81,5 +81,5 @@ Here is a release procefure for releasing.
 Updated documentation
 ---------------------
 
-Sphinx documentation under ``doc/`` directory on the master branch will be automatically uploaded into ReadTheDocs: http://django-redshift-backend.rtfd.io/.
+Sphinx documentation under ``doc/`` directory on the master branch will be automatically uploaded into ReadTheDocs: https://django-redshift-backend.rtfd.io/.
 
diff --git a/doc/index.rst b/doc/index.rst
index 24742bb..2b31be0 100644
--- a/doc/index.rst
+++ b/doc/index.rst
@@ -10,11 +10,11 @@ This is a `Amazon Redshift`_ database backend for Django_.
 
 .. image:: https://img.shields.io/readthedocs/django-redshift-backend/master.svg
    :alt: Read the Docs (master)
-   :target: http://django-redshift-backend.rtfd.io/
+   :target: https://django-redshift-backend.rtfd.io/
 
 .. image:: https://img.shields.io/pypi/v/django-redshift-backend.svg
    :alt: PyPI
-   :target: http://pypi.org/p/django-redshift-backend
+   :target: https://pypi.org/project/django-redshift-backend/
 
 .. image:: https://img.shields.io/pypi/pyversions/django-redshift-backend.svg
    :alt: PyPI - Python Version
diff --git a/doc/refs.rst b/doc/refs.rst
index 51ae9bb..63bf45b 100644
--- a/doc/refs.rst
+++ b/doc/refs.rst
@@ -45,8 +45,8 @@ Amazon Redshift doesn't support RETURNING, so ``last_insert_id`` method retrieve
 
 refs:
 
-* http://stackoverflow.com/q/19428860
-* http://stackoverflow.com/q/25638539
+* https://stackoverflow.com/q/19428860
+* https://stackoverflow.com/q/25638539
 
 In some case, MAX(pk) workaround does not work correctly.
 Bulk insertion makes non-contiguous IDs like: 1, 4, 7, 10, ...
@@ -103,7 +103,7 @@ meta with the custom sortkey type `django_redshift_backend.SortKey` as follow::
 
 `SortKey` in `ordering` are also valid as ordering in Django.
 
-N.B.: there is no validation of this option, instead we let Redshift validate it for you. Be sure to refer to the `documentation <http://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_TABLE_examples.html>`_.
+N.B.: there is no validation of this option, instead we let Redshift validate it for you. Be sure to refer to the `documentation <https://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_TABLE_examples.html>`_.
 
 Using distkey
 -------------