diff --git a/README.md b/README.md
index 179aedc29..3552e99c0 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,7 @@ See https://eslint.vuejs.org
 
 ## :anchor: Versioning Policy
 
-This plugin is following [Semantic Versioning](http://semver.org/) and [ESLint's Semantic Versioning Policy](https://github.com/eslint/eslint#semantic-versioning-policy).
+This plugin is following [Semantic Versioning](https://semver.org/) and [ESLint's Semantic Versioning Policy](https://github.com/eslint/eslint#semantic-versioning-policy).
 
 ## :newspaper: Changelog
 
@@ -30,7 +30,7 @@ See https://eslint.vuejs.org/developer-guide/
 Before you start writing new rule, please read the [official ESLint guide](https://eslint.org/docs/developer-guide/working-with-rules).
 
 Next in order to get an idea how does the AST of the code that you want to check looks like, you can use one of the following applications:
-- [astexplorer.net](http://astexplorer.net/) - best tool to inspect ASTs, but it doesn't support Vue templates yet
+- [astexplorer.net](https://astexplorer.net/) - best tool to inspect ASTs, but it doesn't support Vue templates yet
 - [ast.js.org](https://ast.js.org/) - not fully featured, but supports Vue templates syntax
 
 Since single file components in Vue are not plain JavaScript, we can't use the default parser, and we had to introduce additional one: `vue-eslint-parser`, that generates enhanced AST with nodes that represent specific parts of the template syntax, as well as what's inside the `<script>` tag.
diff --git a/docs/developer-guide/README.md b/docs/developer-guide/README.md
index 074ccc6ec..bdc148105 100644
--- a/docs/developer-guide/README.md
+++ b/docs/developer-guide/README.md
@@ -29,7 +29,7 @@ We're more than happy to see potential contributions, so don't hesitate. If you
 Before you start writing new rule, please read the [official ESLint guide](https://eslint.org/docs/developer-guide/working-with-rules).
 
 Next in order to get an idea how does the AST of the code that you want to check looks like, you can use one of the following applications:
-- [astexplorer.net](http://astexplorer.net/) - best tool to inspect ASTs, but it doesn't support Vue templates yet
+- [astexplorer.net](https://astexplorer.net/) - best tool to inspect ASTs, but it doesn't support Vue templates yet
 - [ast.js.org](https://ast.js.org/) - not fully featured, but supports Vue templates syntax
 
 Since single file components in Vue are not plain JavaScript, we can't use the default parser, and we had to introduce additional one: `vue-eslint-parser`, that generates enhanced AST with nodes that represent specific parts of the template syntax, as well as what's inside the `<script>` tag.
diff --git a/docs/rules/jsx-uses-vars.md b/docs/rules/jsx-uses-vars.md
index f2909b37c..2b27c0645 100644
--- a/docs/rules/jsx-uses-vars.md
+++ b/docs/rules/jsx-uses-vars.md
@@ -9,7 +9,7 @@ description: prevent variables used in JSX to be marked as unused
 
 - :gear: This rule is included in all of `"plugin:vue/base"`, `"plugin:vue/essential"`, `"plugin:vue/strongly-recommended"` and `"plugin:vue/recommended"`.
 
-Since 0.17.0 the ESLint `no-unused-vars` rule does not detect variables used in JSX ([see details](http://eslint.org/blog/2015/03/eslint-0.17.0-released#changes-to-jsxreact-handling)).
+Since 0.17.0 the ESLint `no-unused-vars` rule does not detect variables used in JSX ([see details](https://eslint.org/blog/2015/03/eslint-0.17.0-released#changes-to-jsxreact-handling)).
 This rule will find variables used in JSX and mark them as used.
 
 This rule only has an effect when the `no-unused-vars` rule is enabled.
diff --git a/docs/user-guide/README.md b/docs/user-guide/README.md
index ad0033a13..228370121 100644
--- a/docs/user-guide/README.md
+++ b/docs/user-guide/README.md
@@ -26,7 +26,7 @@ yarn add -D eslint eslint-plugin-vue
 
 ### Configuration
 
-Use `.eslintrc.*` file to configure rules. See also: [http://eslint.org/docs/user-guide/configuring](http://eslint.org/docs/user-guide/configuring).
+Use `.eslintrc.*` file to configure rules. See also: [https://eslint.org/docs/user-guide/configuring](https://eslint.org/docs/user-guide/configuring).
 
 Example **.eslintrc.js**:
 
diff --git a/lib/rules/require-default-prop.js b/lib/rules/require-default-prop.js
index c0d0492e6..6520f5fd2 100644
--- a/lib/rules/require-default-prop.js
+++ b/lib/rules/require-default-prop.js
@@ -1,6 +1,6 @@
 /**
  * @fileoverview Require default value for props
- * @author Michał Sajnóg <msajnog93@gmail.com> (http://github.com/michalsnik)
+ * @author Michał Sajnóg <msajnog93@gmail.com> (https://github.com/michalsnik)
  */
 'use strict'
 
diff --git a/package.json b/package.json
index e8d7149a5..964818c20 100644
--- a/package.json
+++ b/package.json
@@ -29,7 +29,7 @@
   ],
   "author": "Toru Nagashima (https://github.com/mysticatea)",
   "contributors": [
-    "Michał Sajnóg <msajnog93@gmail.com> (http://github.com/michalsnik)"
+    "Michał Sajnóg <msajnog93@gmail.com> (https://github.com/michalsnik)"
   ],
   "license": "MIT",
   "repository": {
diff --git a/tests/lib/rules/require-default-prop.js b/tests/lib/rules/require-default-prop.js
index 7eb689a3d..43d88ed58 100644
--- a/tests/lib/rules/require-default-prop.js
+++ b/tests/lib/rules/require-default-prop.js
@@ -1,6 +1,6 @@
 /**
  * @fileoverview Require default value for props
- * @author Michał Sajnóg <msajnog93@gmail.com> (http://github.com/michalsnik)
+ * @author Michał Sajnóg <msajnog93@gmail.com> (https://github.com/michalsnik)
  */
 'use strict'
 
diff --git a/tools/update-docs.js b/tools/update-docs.js
index 78aac8c1f..288d5a9fc 100644
--- a/tools/update-docs.js
+++ b/tools/update-docs.js
@@ -14,7 +14,7 @@ For example:
 
 - :gear: This rule is included in `"plugin:vue/strongly-recommended"` and `"plugin:vue/recommended"`.
 - :warning: This rule was **deprecated**.
-- :wrench: The `--fix` option on the [command line](http://eslint.org/docs/user-guide/command-line-interface#fix) can automatically fix some of the problems reported by this rule.
+- :wrench: The `--fix` option on the [command line](https://eslint.org/docs/user-guide/command-line-interface#fix) can automatically fix some of the problems reported by this rule.
 ```
 */