diff --git a/doc/global/externalsites/external-resources.qdoc b/doc/global/externalsites/external-resources.qdoc
index 676a5463bf..ec0970e334 100644
--- a/doc/global/externalsites/external-resources.qdoc
+++ b/doc/global/externalsites/external-resources.qdoc
@@ -532,3 +532,7 @@
    \externalpage http://facebook.github.io/zstd/
    \title Zstandard Site
 */
+
+/*!
+    \externalpage https://www.unicode.org/
+    \title Unicode standard
diff --git a/src/corelib/doc/snippets/code/src_corelib_text_qstring.cpp b/src/corelib/doc/snippets/code/src_corelib_text_qstring.cpp
index fade47cfc6..fe44bee4a8 100644
--- a/src/corelib/doc/snippets/code/src_corelib_text_qstring.cpp
+++ b/src/corelib/doc/snippets/code/src_corelib_text_qstring.cpp
@@ -49,7 +49,7 @@
 ****************************************************************************/
 
 //! [1]
-QString url = QLatin1String("http://www.unicode.org/");
+QString url = QLatin1String("https://www.unicode.org/");
 //! [1]
 
 
diff --git a/src/corelib/text/qchar.cpp b/src/corelib/text/qchar.cpp
index c54b80891f..d000fe6bf8 100644
--- a/src/corelib/text/qchar.cpp
+++ b/src/corelib/text/qchar.cpp
@@ -165,7 +165,7 @@ QT_BEGIN_NAMESPACE
     QT_IMPLICIT_QCHAR_CONSTRUCTION.
 
     For more information see
-    \l{http://www.unicode.org/ucd/}{"About the Unicode Character Database"}.
+    \l{https://www.unicode.org/ucd/}{"About the Unicode Character Database"}.
 
     \sa Unicode, QString, QLatin1Char
 */
@@ -173,8 +173,8 @@ QT_BEGIN_NAMESPACE
 /*!
     \enum QChar::UnicodeVersion
 
-    Specifies which version of the \l{http://www.unicode.org/}{Unicode standard}
-    introduced a certain character.
+    Specifies which version of the \l{Unicode standard} introduced a certain
+    character.
 
     \value Unicode_1_1  Version 1.1
     \value Unicode_2_0  Version 2.0
@@ -285,7 +285,7 @@ QT_BEGIN_NAMESPACE
     This enum type defines the Unicode script property values.
 
     For details about the Unicode script property values see
-    \l{http://www.unicode.org/reports/tr24/}{Unicode Standard Annex #24}.
+    \l{https://www.unicode.org/reports/tr24/}{Unicode Standard Annex #24}.
 
     In order to conform to C/C++ naming conventions "Script_" is prepended
     to the codes used in the Unicode Standard.
@@ -462,8 +462,8 @@ QT_BEGIN_NAMESPACE
     \enum QChar::Direction
 
     This enum type defines the Unicode direction attributes. See the
-    \l{http://www.unicode.org/reports/tr9/tr9-35.html#Table_Bidirectional_Character_Types}{Unicode Standard} for a description
-    of the values.
+    \l{https://www.unicode.org/reports/tr9/tr9-35.html#Table_Bidirectional_Character_Types}{Unicode
+    Standard} for a description of the values.
 
     In order to conform to C/C++ naming conventions "Dir" is prepended
     to the codes used in the Unicode Standard.
@@ -499,8 +499,7 @@ QT_BEGIN_NAMESPACE
     \enum QChar::Decomposition
 
     This enum type defines the Unicode decomposition attributes. See
-    the \l{http://www.unicode.org/}{Unicode Standard} for a
-    description of the values.
+    the \l{Unicode Standard} for a description of the values.
 
     \value NoDecomposition
     \value Canonical
@@ -529,7 +528,7 @@ QT_BEGIN_NAMESPACE
     since 5.3
 
     This enum type defines the Unicode joining type attributes. See the
-    \l{http://www.unicode.org/}{Unicode Standard} for a description of the values.
+    \l{Unicode Standard} for a description of the values.
 
     In order to conform to C/C++ naming conventions "Joining_" is prepended
     to the codes used in the Unicode Standard.
@@ -550,8 +549,7 @@ QT_BEGIN_NAMESPACE
     \internal
 
     This enum type defines names for some of the Unicode combining
-    classes. See the \l{http://www.unicode.org/}{Unicode Standard}
-    for a description of the values.
+    classes. See the \l{Unicode Standard} for a description of the values.
 
     \value Combining_Above
     \value Combining_AboveAttached
diff --git a/src/corelib/text/qlocale.cpp b/src/corelib/text/qlocale.cpp
index 5f3e859667..c2c0546643 100644
--- a/src/corelib/text/qlocale.cpp
+++ b/src/corelib/text/qlocale.cpp
@@ -245,7 +245,7 @@ bool operator<(const LikelyPair &lhs, const LikelyPair &rhs)
     is no more specific recommendation available.
 
     For the formal specification, see
-    http://www.unicode.org/reports/tr35/#Likely_Subtags
+    https://www.unicode.org/reports/tr35/#Likely_Subtags
 
     \note We also search und_script_region and und_region; they're not mentioned
     in the spec, but the examples clearly presume them and CLDR does provide
diff --git a/src/corelib/text/qstring.cpp b/src/corelib/text/qstring.cpp
index c98e4ba6d9..6badf9b5c1 100644
--- a/src/corelib/text/qstring.cpp
+++ b/src/corelib/text/qstring.cpp
@@ -7553,7 +7553,7 @@ QList<QStringView> QStringView::split(const QRegularExpression &re, Qt::SplitBeh
     \value NormalizationForm_KC  Compatibility Decomposition followed by Canonical Composition
 
     \sa normalized(),
-        {http://www.unicode.org/reports/tr15/}{Unicode Standard Annex #15}
+        {https://www.unicode.org/reports/tr15/}{Unicode Standard Annex #15}
 */
 
 /*!
diff --git a/src/corelib/text/qtextboundaryfinder.cpp b/src/corelib/text/qtextboundaryfinder.cpp
index 797cd07bd6..0ac2cec3ff 100644
--- a/src/corelib/text/qtextboundaryfinder.cpp
+++ b/src/corelib/text/qtextboundaryfinder.cpp
@@ -73,8 +73,8 @@ static void init(QTextBoundaryFinder::BoundaryType type, QStringView str, QCharA
 
     QTextBoundaryFinder allows to find Unicode text boundaries in a
     string, accordingly to the Unicode text boundary specification (see
-    \l{http://www.unicode.org/reports/tr14/}{Unicode Standard Annex #14} and
-    \l{http://www.unicode.org/reports/tr29/}{Unicode Standard Annex #29}).
+    \l{https://www.unicode.org/reports/tr14/}{Unicode Standard Annex #14} and
+    \l{https://www.unicode.org/reports/tr29/}{Unicode Standard Annex #29}).
 
     QTextBoundaryFinder can operate on a QString in four possible
     modes depending on the value of \a BoundaryType.
@@ -85,17 +85,17 @@ static void init(QTextBoundaryFinder::BoundaryType type, QStringView str, QCharA
     for example form one grapheme cluster as the user thinks of them
     as one character, yet it is in this case represented by two
     unicode code points
-    (see \l{http://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries}).
+    (see \l{https://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries}).
 
     Word boundaries are there to locate the start and end of what a
     language considers to be a word
-    (see \l{http://www.unicode.org/reports/tr29/#Word_Boundaries}).
+    (see \l{https://www.unicode.org/reports/tr29/#Word_Boundaries}).
 
     Line break boundaries give possible places where a line break
     might happen and sentence boundaries will show the beginning and
     end of whole sentences
-    (see \l{http://www.unicode.org/reports/tr29/#Sentence_Boundaries} and
-    \l{http://www.unicode.org/reports/tr14/}).
+    (see \l{https://www.unicode.org/reports/tr29/#Sentence_Boundaries} and
+    \l{https://www.unicode.org/reports/tr14/}).
 
     The first position in a string is always a valid boundary and
     refers to the position before the first character. The last