diff --git a/Engine/Commands/GetScriptAnalyzerRuleCommand.cs b/Engine/Commands/GetScriptAnalyzerRuleCommand.cs
index a0a669b98..e60ff8500 100644
--- a/Engine/Commands/GetScriptAnalyzerRuleCommand.cs
+++ b/Engine/Commands/GetScriptAnalyzerRuleCommand.cs
@@ -23,7 +23,7 @@ namespace Microsoft.Windows.PowerShell.ScriptAnalyzer.Commands
     /// <summary>
     /// GetScriptAnalyzerRuleCommand: Cmdlet to list all the analyzer rule names and descriptions.
     /// </summary>
-    [Cmdlet(VerbsCommon.Get, "ScriptAnalyzerRule", HelpUri = "http://go.microsoft.com/fwlink/?LinkId=525913")]
+    [Cmdlet(VerbsCommon.Get, "ScriptAnalyzerRule", HelpUri = "https://go.microsoft.com/fwlink/?LinkId=525913")]
     public class GetScriptAnalyzerRuleCommand : PSCmdlet, IOutputWriter
     {
         #region Parameters
diff --git a/Engine/Commands/InvokeScriptAnalyzerCommand.cs b/Engine/Commands/InvokeScriptAnalyzerCommand.cs
index 4719a51a1..7f7a76a41 100644
--- a/Engine/Commands/InvokeScriptAnalyzerCommand.cs
+++ b/Engine/Commands/InvokeScriptAnalyzerCommand.cs
@@ -39,7 +39,7 @@ namespace Microsoft.Windows.PowerShell.ScriptAnalyzer.Commands
         "ScriptAnalyzer",
         DefaultParameterSetName = "File",
         SupportsShouldProcess = true,
-        HelpUri = "http://go.microsoft.com/fwlink/?LinkId=525914")]
+        HelpUri = "https://go.microsoft.com/fwlink/?LinkId=525914")]
     public class InvokeScriptAnalyzerCommand : PSCmdlet, IOutputWriter
     {
         #region Private variables
diff --git a/Engine/Settings/CodeFormattingStroustrup.psd1 b/Engine/Settings/CodeFormattingStroustrup.psd1
index 51cbb540a..f40c83988 100644
--- a/Engine/Settings/CodeFormattingStroustrup.psd1
+++ b/Engine/Settings/CodeFormattingStroustrup.psd1
@@ -1,4 +1,4 @@
-# Inspired by http://eslint.org/docs/rules/brace-style#stroustrup
+# Inspired by https://eslint.org/docs/rules/brace-style#stroustrup
 @{
     IncludeRules = @(
         'PSPlaceOpenBrace',
diff --git a/Engine/VariableAnalysisBase.cs b/Engine/VariableAnalysisBase.cs
index 79fd6727c..2ace1910e 100644
--- a/Engine/VariableAnalysisBase.cs
+++ b/Engine/VariableAnalysisBase.cs
@@ -546,7 +546,7 @@ internal static void DominanceFrontiers(List<Block> Blocks, Block Entry)
         /// <summary>
         /// Returns the immediate dominator of each block. The array returned is
         /// indexed by postorder number of each block.
-        /// Based on http://www.cs.rice.edu/~keith/Embed/dom.pdf
+        /// Based on https://www.cs.rice.edu/~keith/Embed/dom.pdf
         /// </summary>
         /// <param name="entry"></param>
         /// <param name="Blocks"></param>
diff --git a/PowerShellBestPractices.md b/PowerShellBestPractices.md
index 62838a856..81bc3e00c 100644
--- a/PowerShellBestPractices.md
+++ b/PowerShellBestPractices.md
@@ -126,6 +126,6 @@ The following guidelines come from a combined effort from both the PowerShell te
 ###Reference:
 * Cmdlet Development Guidelines from MSDN site (Cmdlet Development Guidelines): https://msdn.microsoft.com/en-us/library/ms714657(v=vs.85).aspx 
 * The Community Book of PowerShell Practices (Compiled by Don Jones and Matt Penny and the Windows PowerShell Community): https://powershell.org/community-book-of-powershell-practices/
-* PowerShell DSC Resource Design and Testing Checklist: http://blogs.msdn.com/b/powershell/archive/2014/11/18/powershell-dsc-resource-design-and-testing-checklist.aspx
+* PowerShell DSC Resource Design and Testing Checklist: https://blogs.msdn.com/b/powershell/archive/2014/11/18/powershell-dsc-resource-design-and-testing-checklist.aspx
 * DSC Guidelines can also be found in the DSC Resources Repository: https://github.com/PowerShell/DscResources
 * The Unofficial PowerShell Best Practices and Style Guide: https://github.com/PoshCode/PowerShellPracticeAndStyle
diff --git a/README.md b/README.md
index d8b30ad56..bcb1cb083 100644
--- a/README.md
+++ b/README.md
@@ -353,7 +353,7 @@ Contributing to ScriptAnalyzer
 ==============================
 You are welcome to contribute to this project. There are many ways to contribute:
 
-1. Submit a bug report via [Issues]( https://github.com/PowerShell/PSScriptAnalyzer/issues). For a guide to submitting good bug reports, please read [Painless Bug Tracking](http://www.joelonsoftware.com/articles/fog0000000029.html).
+1. Submit a bug report via [Issues]( https://github.com/PowerShell/PSScriptAnalyzer/issues). For a guide to submitting good bug reports, please read [Painless Bug Tracking](https://www.joelonsoftware.com/articles/fog0000000029.html).
 2. Verify fixes for bugs.
 3. Submit your fixes for a bug. Before submitting, please make sure you have:
   * Performed code reviews of your own
@@ -366,7 +366,7 @@ You are welcome to contribute to this project. There are many ways to contribute
 7. Tell others about the project.
 8. Tell the developers how much you appreciate the product!
 
-You might also read these two blog posts about contributing code: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza, and [Don’t “Push” Your Pull Requests](http://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik.
+You might also read these two blog posts about contributing code: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza, and [Don’t “Push” Your Pull Requests](https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik.
 
 Before submitting a feature or substantial code contribution, please discuss it with the Windows PowerShell team via [Issues](https://github.com/PowerShell/PSScriptAnalyzer/issues), and ensure it follows the product roadmap. Note that all code submissions will be rigorously reviewed by the Windows PowerShell Team. Only those that meet a high bar for both quality and roadmap fit will be merged into the source.
 
diff --git a/RuleDocumentation/ProvideCommentHelp.md b/RuleDocumentation/ProvideCommentHelp.md
index ddfc914bc..bfd922c63 100644
--- a/RuleDocumentation/ProvideCommentHelp.md
+++ b/RuleDocumentation/ProvideCommentHelp.md
@@ -6,7 +6,7 @@
 
 Comment based help should be provided for all PowerShell commands. This test only checks for the presence of comment based help and not on the validity or format.
 
-For assistance on comment based help, use the command ```Get-Help about_comment_based_help``` or the article, "How to Write Cmdlet Help" (http://go.microsoft.com/fwlink/?LinkID=123415).
+For assistance on comment based help, use the command ```Get-Help about_comment_based_help``` or the article, "How to Write Cmdlet Help" (https://go.microsoft.com/fwlink/?LinkID=123415).
 
 ## Configuration
 
diff --git a/Tests/Rules/GoodCmdlet.ps1 b/Tests/Rules/GoodCmdlet.ps1
index c667cb5f1..4f04f5c74 100644
--- a/Tests/Rules/GoodCmdlet.ps1
+++ b/Tests/Rules/GoodCmdlet.ps1
@@ -25,7 +25,7 @@ function Get-File
     [CmdletBinding(DefaultParameterSetName='Parameter Set 1',
                   SupportsShouldProcess=$true,
                   PositionalBinding=$false,
-                  HelpUri = 'http://www.microsoft.com/',
+                  HelpUri = 'https://www.microsoft.com/',
                   ConfirmImpact='Medium')]
     [Alias()]
     [OutputType([String], [System.Double], [Hashtable], "MyCustom.OutputType")]
@@ -134,7 +134,7 @@ function Get-Folder
     [CmdletBinding(DefaultParameterSetName='Parameter Set 1',
                   SupportsShouldProcess,
                   PositionalBinding=$false,
-                  HelpUri = 'http://www.microsoft.com/',
+                  HelpUri = 'https://www.microsoft.com/',
                   ConfirmImpact='Medium')]
     [Alias()]
     [OutputType([String], [System.Double], [Hashtable], "MyCustom.OutputType")]