{"id":8146,"date":"2017-02-15T20:00:51","date_gmt":"2017-02-16T01:00:51","guid":{"rendered":"https:\/\/www.psafe.com\/en\/blog\/?p=8146"},"modified":"2017-03-06T17:35:57","modified_gmt":"2017-03-06T22:35:57","slug":"common-passwords-ranked","status":"publish","type":"post","link":"https:\/\/www.psafe.com\/en\/blog\/common-passwords-ranked\/","title":{"rendered":"Here Are the Most Common Passwords, Ranked"},"content":{"rendered":"

It\u2019s difficult to navigate through this confusing, technological age. But luckily, some of it is pretty straightforward. When it comes to passwords, most websites \u2014 if they’re reliable \u2014 will call for certain requirements. Perhaps a minimum set of characters. At least one uppercase letter. Sometimes, they ask for one special character, like a dash or period. Before reading about which passwords <\/span>not<\/span><\/i> to use, activate Applock so you\u2019ll be ready to protect your most sensitive apps with a very secure second password:<\/span><\/p>\n

\"deeplink_vault\"<\/a><\/center>
\nWebsite administrators invested in the cybersecurity of their users have tried to make some standards blatantly obvious. For example, if you’re trying to create a secure password, don’t use the word “password.” Please don’t use the word “google.” And please, do not type “7” seven times in a row, because it never works out in the end. <\/span><\/p>\n

Still, the most popular passwords of the last few years haven’t changed much.<\/span><\/p>\n

This now means that because the average password-creating user \u2014 in spite of presumably being versed in the basics of cybersecurity \u2014 isn’t inclined to maximize his protection on his own, site operators may have to step it up.<\/span> Keeper Security<\/span><\/i> released a study on the most common passwords of 2016, gathering data from 10 million password-protected accounts breached in the past year. The top twenty five most frequently used passwords accounted for 50% of the 10 million cases studied, displayed below.<\/span><\/p>\n

Top Ranking Passwords<\/b><\/p>\n

    \n
  1. 123456<\/span><\/li>\n
  2. 123456789 <\/span><\/li>\n
  3. qwerty <\/span><\/li>\n
  4. 12345678 <\/span><\/li>\n
  5. 111111<\/span><\/li>\n
  6. 1234567890<\/span><\/li>\n
  7. 1234567<\/span><\/li>\n
  8. password <\/span><\/li>\n
  9. 123123<\/span><\/li>\n
  10. 987654321 <\/span><\/li>\n
  11. qwertyuiop<\/span><\/li>\n
  12. mynoob<\/span><\/li>\n
  13. 123321<\/span><\/li>\n
  14. 666666<\/span><\/li>\n
  15. 18atcskd2w<\/span><\/li>\n
  16. 7777777<\/span><\/li>\n
  17. 1q2w3e4r<\/span><\/li>\n
  18. 654321<\/span><\/li>\n
  19. 555555<\/span><\/li>\n
  20. 3rjs1la7qe <\/span><\/li>\n
  21. google<\/span><\/li>\n
  22. 1q2w3e4r5t <\/span><\/li>\n
  23. 123qwe <\/span><\/li>\n
  24. zxcvbnm <\/span><\/li>\n
  25. 1q2w3e<\/span><\/li>\n<\/ol>\n

    The password “123456” accounted for about 17% of the compromised passwords evaluated by <\/span>Keeper. <\/span><\/i>Similarly, other fairly predictable number sequences like “987654321” and “666666” made it onto the list \u2014 their predictability lying in the arrangement of keys on the keyboard and matching the number of characters to the number given, respectively. Letter sequences such as “qwerty” were also decipherable by hackers who were familiar with keyboard layouts. In addition, full words like “google” were fair game for hackers trying to gain access to Gmail accounts.<\/span><\/p>\n

    Seemingly random passwords like “3rjs1la7qe” were attributed to bots attempting to send spam emails. These were made vulnerable by the mere principle of repetition; as bots used these passwords over and over again, hackers caught on.<\/p>\n

    Human beings, known for their surprises, also managed to get “mynoob” onto the most common passwords list \u2014 proving that there are still mysteries in the world.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

    It can be hard to create a password that no one will be able to guess. To help you out, here are some passwords you definitely shouldn\u2019t use.<\/p>\n","protected":false},"author":83,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","footnotes":""},"categories":[5],"tags":[],"class_list":["post-8146","post","type-post","status-publish","format-standard","hentry","category-security"],"_links":{"self":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts\/8146","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/users\/83"}],"replies":[{"embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/comments?post=8146"}],"version-history":[{"count":0,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts\/8146\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/media?parent=8146"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/categories?post=8146"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/tags?post=8146"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}