{"id":90,"date":"2026-11-16T09:03:00","date_gmt":"2026-11-16T08:03:00","guid":{"rendered":"https:\/\/www.strongrandompassword.com\/blog\/?p=90"},"modified":"2026-11-15T09:33:29","modified_gmt":"2026-11-15T08:33:29","slug":"recovery-codes-print-store-verify","status":"publish","type":"post","link":"https:\/\/www.strongrandompassword.com\/blog\/recovery-codes-print-store-verify\/","title":{"rendered":"Recovery Codes: Print, Store, Verify"},"content":{"rendered":"<p><strong>TL;DR \/ Summary:<\/strong> Recovery codes are the last way into an account, and most people store them badly or never test them. Print once, store offline in two places, and verify that at least one code works before you need it.<\/p>\n<h2>Why recovery codes exist<\/h2>\n<p>Two-factor authentication depends on a device. When the device is lost, broken, or replaced, the account becomes inaccessible unless there is another path in.<\/p>\n<p>Recovery codes are that path. They are single-use, they bypass the second factor, and they are usually the only fallback that does not require a support request.<\/p>\n<p>Because they are powerful, they are also sensitive. A leaked recovery code is equivalent to a stolen second factor, which is why storage matters as much as generation.<\/p>\n<h2>Print, do not screenshot<\/h2>\n<p>A screenshot sits in a photo library that syncs to the cloud and is indexed by search. That is convenient and it is the most common way recovery codes leak.<\/p>\n<p>Print the codes, or write them by hand. Paper has the property of not being remotely accessible, which is exactly what a recovery code needs.<\/p>\n<p>If printing feels wasteful, print once and store the sheet, rather than regenerating codes repeatedly. Regenerating invalidates all previous codes.<\/p>\n<ul>\n<li><strong>Paper copy<\/strong> \u2014 one at home, one elsewhere<\/li>\n<li><strong>Password manager<\/strong> \u2014 acceptable as a secondary copy, with a strong master password<\/li>\n<li><strong>Encrypted file<\/strong> \u2014 acceptable if the key is stored separately<\/li>\n<li><strong>Cloud notes<\/strong> \u2014 avoid; convenient for you and for an attacker<\/li>\n<\/ul>\n<h3>Two physical locations<\/h3>\n<p>One copy at home and one somewhere else\u2014a safe deposit box, a trusted family member, a locked drawer at work. A single copy is one fire away from useless.<\/p>\n<p>Tell one trusted person where the second copy is, without telling them what it is for. That single sentence is the difference between a recoverable and an unrecoverable account.<\/p>\n<h2>Verify a code works<\/h2>\n<p>Testing a recovery code consumes it, which is why people skip the test. Regenerate codes, test one, and store the remaining set.<\/p>\n<p>The test is worth it. A set of codes that were printed from an old session, or that belong to a different account, is a set that will fail at the worst possible moment.<\/p>\n<p>Do the test during a quiet moment, not during a crisis. And do it on the same account you will need to recover.<\/p>\n<blockquote><p>An untested recovery code is a hope, not a backup.<\/p><\/blockquote>\n<h2>When to regenerate<\/h2>\n<p>Regenerate after any suspected compromise, after losing a device that had access, and after using a code. Some systems require regeneration when the last code is used.<\/p>\n<p>Regenerating invalidates every previous code. That is the point, and it is also the reason to be careful: regenerating and then failing to store the new set leaves you with none.<\/p>\n<p>Keep a note of the regeneration date. A set of codes from four years ago may still work, or may have been invalidated by a policy change, and knowing the date helps you decide whether to regenerate.<\/p>\n<h2>Storage that survives<\/h2>\n<p>Paper degrades, gets thrown away in a tidy-up, and occasionally gets photographed and posted. Store it in something that will not be mistaken for rubbish.<\/p>\n<p>A labelled envelope inside a folder of important documents is a reasonable home. An unlabelled scrap in a drawer is not, because nobody will know what it is.<\/p>\n<p>Label it in a way that is clear to you and opaque to a casual finder. &#8220;Recovery codes \u2014 account, date&#8221; is a reasonable compromise.<\/p>\n<h2>What to do if the codes are lost<\/h2>\n<p>Contact the provider immediately. Most have an identity verification process, and it is usually slow and sometimes unsuccessful.<\/p>\n<p>If the account is critical, start the recovery process before the device is actually lost. Knowing the process is faster than learning it under pressure.<\/p>\n<p>Check whether the provider offers multiple second factors. A hardware key plus recovery codes is more resilient than a phone plus recovery codes, because the phone can be lost with the codes.<\/p>\n<h2>A short routine<\/h2>\n<p>When you enable two-factor authentication, print the codes immediately, store one copy, and put the second copy somewhere else the same week.<\/p>\n<p>Set a reminder to check the set annually. Codes do not expire on a schedule, but accounts change and providers migrate.<\/p>\n<p>For generating and storing the passwords that protect the account in the first place, <a href=\"https:\/\/www.strongrandompassword.com\/\">strong random password<\/a> is a reasonable starting point, though the recovery codes should stay on paper.<\/p>\n<p>Recovery codes are boring until the day they are the only thing standing between you and a locked account. Printing them takes two minutes, and it is the cheapest insurance in account security.<\/p>\n<h2>Sharing access without sharing codes<\/h2>\n<p>Recovery codes should not be shared, even with a partner, unless the account is genuinely joint. Sharing a recovery code is equivalent to sharing the second factor.<\/p>\n<p>For joint accounts, use separate second factors for each person rather than one shared code set. Many services support multiple authenticator devices.<\/p>\n<p>Document who holds which copy. If two people both believe they hold the only copy, neither will check, and both will be surprised.<\/p>\n<h3>When a device is replaced<\/h3>\n<p>Replacing a phone is the most common moment a second factor becomes unavailable. Before wiping the old device, confirm the new one is enrolled and working.<\/p>\n<p>Check the recovery codes at the same time. A device change is a natural point to regenerate them, particularly if the old phone is being sold or recycled.<\/p>\n<p>Wipe the old device properly. A phone that is reset but still signed in to an account is a security problem that outlasts the upgrade.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR \/ Summary: Recovery codes are the last way into an account, and most people store them badly or never test them. Print once, store offline in two places, and verify that at least one code works before you need it. Why recovery codes exist Two-factor authentication depends on a device. When the device is &#8230; <a title=\"Recovery Codes: Print, Store, Verify\" class=\"read-more\" href=\"https:\/\/www.strongrandompassword.com\/blog\/recovery-codes-print-store-verify\/\" aria-label=\"Read more about Recovery Codes: Print, Store, Verify\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":37,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-90","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-security-practices"],"_links":{"self":[{"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/posts\/90","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/comments?post=90"}],"version-history":[{"count":1,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/posts\/90\/revisions"}],"predecessor-version":[{"id":91,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/posts\/90\/revisions\/91"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/media\/37"}],"wp:attachment":[{"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/media?parent=90"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/categories?post=90"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/tags?post=90"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}