ID
Menu
How NOPKEY works

Plan your keys. Record what they protect. See what needs attention.

See how many Primary and Backup Keys fit your needs, record where each physical Key is used, and let NOPKEY show what may need attention.

01Plan your Keys
02Record what they protect
03See what needs attention
Three simple steps

From a setup plan to a clear next step.

Plan the setup, create a record for each physical Key, and use those records to spot gaps or changes.

01

Plan your Primary and Backup Keys

Answer a few questions to see a setup that fits how you use and store your Security Keys.

  • How many Keys you may need
  • What each Key is for
  • Where to keep your Backups
02

Record what each Key protects

Name the physical Key, choose its role, and record the accounts and services where you use it.

  • Key name, model, and role
  • Accounts and services it protects
  • Where the physical Key is kept

You maintain these records. NOPKEY does not independently check third-party accounts.

03

See what needs attention

NOPKEY compares your plan with the records you maintain and shows specific items to review.

  • Services without a recorded Backup
  • Key records that may be outdated
  • Services affected by loss or replacement
One physical identity

Scan one label. Open the right Key record.

A NOPKEY ID connects the Security Key in your hand to its private management record.

NOPKEY ID

The label opens the record.

Scan the QR code on a phone, or enter the printed ID on a computer. After sign-in, you can view and maintain the correct Key record.

Physical KeyThe item you carry
ID LabelScan or enter
Private recordOpen after sign-in

The ID identifies a record. It does not unlock the Security Key or any account.

What NOPKEY helps you see

Three useful answers from the same Key records.

Record each detail once. NOPKEY connects it to the questions that matter later.

01

Find Keys by service

Search an account or service and see which physical Keys are recorded for it.

02

Spot missing Backups

See where a planned Backup is missing and which Key records may need review.

03

See loss or replacement impact

See which services may need action and what still needs to move to a replacement Key.

Real situations

See how a record becomes a clear next step.

These examples show the kind of guidance NOPKEY can produce from the records you maintain.

Backup gap

AWS has no recorded Backup Key

AWS is recorded on the Primary Key, but not on a Backup Key in the same setup.

Recorded situationOffice Key · Primary
No Backup Key recorded
Recommended action

Add AWS to a Backup Key, then record it in NOPKEY.

Review recommended

Office Key may need a registration review

The services recorded for this physical Key have not been reviewed recently.

Recorded situationOffice Key
Last reviewed 11 months ago
Recommended action

Review its recorded services and update anything that changed.

Lost-key impact

Travel Key was marked as lost

Three services are recorded as using this physical Security Key.

Services that may be affectedGitHub · Google · AWS
Recommended action

Review these 3 services and begin the replacement process.

Examples are illustrative. Guidance is calculated from records maintained by you or your Team.

How guidance is created

You record the facts. NOPKEY shows the answers.

NOPKEY does not read credentials or independently verify third-party accounts.

You record

What you know about each Key

Only the management details needed to keep the physical Key understandable.

  • Key name, model, role, and Key Set
  • Accounts and services where you use it
  • Where the physical Key is kept
  • Whether it is active, lost, replaced, or retired
NOPKEY shows

What may need your attention

Useful answers calculated from the records you maintain.

  • Which physical Keys are recorded for each service
  • Where a Backup has not been recorded
  • Which records may need review
  • What loss or replacement may affect

NOPKEY highlights what may need attention. You review and confirm changes in the actual service.

When a Key changesWhat happens if a Key is lost, recovered, replaced, or retired?

A Key record stays useful as its status changes, so you can understand what happened and what may still need action.

ActiveKeep its identity, role, services, and location current.
LostSee affected services and begin recovery or replacement.
RecoveredReturn it to use and review changes already made.
ReplacedTrack services that still need the new Key.
RetiredKeep its history without counting it as a current Key.

NOPKEY keeps the record and history together. It does not revoke registrations in third-party services for you.

Personal or Team

Use the same simple records at the level you need.

Manage your own Keys, or add people, assignments, and shared oversight for an organization.

Personal

Manage your own Keys

Plan Primary and Backup Keys, record where they are used, and manage loss or replacement.

  • Up to 10 Security Keys
  • Setup Planner and printable NOPKEY IDs
  • Backup gaps and Needs Attention guidance
Team

Coordinate Keys across people

Add holders, assignments, shared Backup planning, and Key history.

  • Team workspace and Key holders
  • Shared Backup planning and recovery context
  • Assignment and Key history
Privacy by design

Identify the Key—not the secret.

NOPKEY organizes physical Security Key records and coverage without storing authentication secrets.

No passwordsNo PINsNo passkeysNo private keysNo recovery codesNo credentials
Ready to start?

Plan your setup or open an existing Key.

Get a recommended Primary and Backup setup, or use a NOPKEY ID to open the correct Key record.

Personal Free · Up to 10 Security Keys