Skip to content
Novaz AuthenticatorGET

BuiltWith 2FA: how to set up an authenticator app

By the Novaz team · Updated October 29, 2026
Novaz steps checked against version 1.0.5

On this page
  1. Turn on 2FA with an authenticator app
  2. No backup codes in sight
  3. Passkeys and team SSO are separate
  4. When BuiltWith asks for a code
  5. If BuiltWith rejects your code
  6. Changing phones or turning 2FA off
  7. If you lose your authenticator
  8. Official BuiltWith help

BuiltWith is the web technology lookup and lead list service: you sign in to build reports of sites using a given platform, export them, and manage your plan. Two-factor authentication (2FA) is optional on a BuiltWith account, and it works with an authenticator app. BuiltWith's only how-to for it is a short demo video in its knowledge base, plus a direct link to the setup page for people who are already signed in (BuiltWith). This guide walks through what that video shows and points out what it leaves out. We use Authenticator App - Novaz on iPhone, but any authenticator app works the same way.

How we checked this guide: the BuiltWith steps come from BuiltWith's own knowledge base, linked below, mostly from the screens shown in its 2FA demo video, which we watched on October 21, 2026. We haven't tested them on a BuiltWith account, so a label may differ slightly. BuiltWith's sign-in and setup pages show a human check to automated visitors, so we couldn't read them directly. The Novaz steps are checked against the app, version 1.0.5.

Turn on 2FA with an authenticator app

  1. Sign in to BuiltWith on a computer. Open the Account menu at the top and choose Manage Account.
  2. On the Account Settings page, find the Two Factor Authentication card and select 2FA Configuration. You can also go straight to builtwith.com/2fa-setup while signed in (BuiltWith).
  3. The Two Factor Authentication Setup page asks you to "use Google Authenticator or similar tool to scan this QR Code." Any app that makes time-based codes counts as a similar tool.
  4. In Novaz, tap +, then Scan QR code, and point the camera at the screen. If BuiltWith is open on the same iPhone, take a screenshot, tap +, then Choose a photo. See scanning a QR code on the same iPhone.
  5. If scanning doesn't work, use the long string of letters and numbers printed under the QR code. It has no label on the page, but it's the setup key. In Novaz, tap +, then Enter key manually, type a name such as BuiltWith in Service, and paste or type the string into Setup key. See What is a 2FA setup key?
  6. Type the 6-digit code from Novaz into the six boxes and select Enable.

The page then confirms that 2FA is on for your account and offers a Back to Dashboard button (BuiltWith). The video doesn't say how often codes change, so scanning the QR code is the safer choice: it carries the code settings with it.

No backup codes in sight

The demo goes straight from Enable to the confirmation screen. It shows no backup or recovery codes, and the knowledge base doesn't mention any. Plan around that. In Novaz, turn on iCloud backup or export a backup file, so a lost iPhone doesn't take your codes with it. If you have no Novaz backup, nothing in BuiltWith's documentation gets you a code another way. Before you rely on 2FA, make sure you know how you'd reach BuiltWith support (below). General advice on spare sign-in options is in 2FA backup codes.

Passkeys and team SSO are separate

The Account Settings page has a Passkeys card next to the 2FA one, with its own Passkeys Configuration button. BuiltWith's older passkey article sends you to builtwith.com/2fa-setup?PK=true and says to choose the passkey option on the sign-in screen afterwards (BuiltWith). It doesn't say whether a passkey can stand in for the authenticator code if you lose your phone.

Teams on BuiltWith Pro can also sign in through SAML single sign-on, which BuiltWith turns on at no extra cost (BuiltWith). If your company signs you in that way, your company's identity provider decides how 2FA works.

When BuiltWith asks for a code

BuiltWith's pages don't describe the sign-in step after 2FA is on, or whether it remembers trusted browsers. Expect to type a Novaz code when you sign in.

If BuiltWith rejects your code

BuiltWith has no help page on rejected codes. Start with the iPhone's clock: Settings > General > Date & Time > Set Automatically. Novaz warns you when the clock is 15 seconds or more off. If you're still setting up, check that you typed all six digits before the code changed. More causes are in Authenticator code not working?

Changing phones or turning 2FA off

Once 2FA is on, the setup page in the demo shows a Disable 2FA button (BuiltWith). BuiltWith doesn't describe a phone switch, and the video doesn't show what happens after you select that button. The practical route while you still have the old phone: turn 2FA off, then set it up again with the new one. If you back up Novaz with iCloud backup or a backup file, you can restore it on the new iPhone and skip that. See How to transfer your authenticator app to a new iPhone.

If you lose your authenticator

BuiltWith's knowledge base has no recovery article for a lost authenticator, and it doesn't say what proof it asks for or how long a reset takes. The contact listed on its FAQ page is support@builtwith.com (BuiltWith). It helps to write from the email address on your account. Steps to take while you wait are in Lost the phone with your authenticator app?

Official BuiltWith help