Peti Alat Keselamatan & Diagnostik 2FA / TOTP
Suite diagnostik khas yang dibina untuk penyelesaian masalah 2FA dan jurutera keselamatan. Sahkan & baiki rahsia Base32, huraikan dan bina URI otpauth:// dwiarah dengan kod QR langsung, dan ukur hanyutan jam peranti dengan ketepatan milisaat.
Pengesah & Pembersih Kunci Base32
Mengesan aksara tidak sah (0, 1, 8, 9, O, I, L), membuang ruang putih/sempang, menambah pelapik '=', dan mengelompokkan kepada blok standard 4 aksara
Aksara Tidak Mematuhi Dikesan
💡 Uji kunci yang disahkan serta-merta dalam penjana utama dengan pengiraan TOTP 6 digit segera.
🚀 Ujian Satu Klik dalam Penjana 2FAPemeriksa URI & Pembina Songsang otpauth://
Penyuntingan dwiarah: Huraikan URI otpauth:// mentah kepada medan, atau edit medan untuk menjana URI bersih dan kod QR langsung
Scan with Google Authenticator, Microsoft Authenticator, or 1Password to bind instantly
NTP System Clock Drift Inspector
Multi-sample network round-trip measurement against reference time. Diagnoses 90%+ of 2FA verification errors.
Perfect Clock Sync (Offset < 1s)
Your device system clock is in perfect synchronization with global network standard time. RFC 6238 30-second TOTP tokens will generate and authenticate reliably without window desynchronization.
Panduan Penentukuran Masa Sistem (Baiki Kegagalan Kod 2FA)
Pilih sistem pengendalian anda- Press Win + I to open Tetapan Windows.
- Select Time & language from the sidebar, then click Date & time.
- Ensure that Set time automatically and Set time zone automatically are both toggled ON.
- Under Additional settings, click the Sync now button until a green checkmark appears.
- CLI Command (Admin): Run
w32tm /resyncin PowerShell or CMD.
- Click the Apple menu in the top-left corner and open System Settings.
- Navigate to General in the sidebar, then click Date & Time.
- Ensure Set time and date automatically is enabled.
- Keep the default reference server set to
time.apple.com. - Terminal Command: Open Terminal and run
sudo sntp -sS time.apple.com.
- Open the Settings app on your iPhone or iPad.
- Tap General, then select Date & Time.
- Ensure Set Automatically is toggled ON.
- 💡 Pro Tip: If it was already on but drift persists, toggle it OFF for 5 seconds, then toggle it ON again to force an immediate base station re-sync.
- Open your phone's Settings and tap System > Date & time.
- Enable Use network-provided time and Use network-provided time zone.
- ⭐ Google Authenticator built-in sync: Open Google Authenticator > Tap the 3 dots menu > Settings > Time correction for codes > Tap Sync now.
Frequently Asked Questions (FAQ)
In-depth technical answers on Base32 encoding, otpauth standards, and clock drift mechanics
Q. Why are digits 0, 1, 8, and 9 invalid in Base32?
Under RFC 4648, standard Base32 represents 5 bits of data per character, requiring exactly 32 distinct symbols: uppercase A-Z (26 letters) and digits 2-7 (6 numbers). Digits 0, 1, 8, and 9 simply do not exist in the alphabet. Furthermore, 0 is easily confused with letter O, and 1 is easily confused with I or L. Our auto-fix utility restores accidentally confused characters automatically.
Q. What parameters are included in an otpauth:// URI?
The otpauth:// specification originated with Google Authenticator and has become an RFC-aligned open standard. Key parameters include: secret (Base32 shared key), issuer (provider name, e.g. GitHub or Google), algorithm (HMAC hash function, default SHA1), digits (code length, default 6), and period (time step window, default 30s).
Q. Why does a clock drift of 15 seconds cause token rejection?
TOTP computes dynamic codes strictly via T = Math.floor(UnixTimestamp / 30). While most authentication servers provide a ±1 interval window tolerance, when your local device clock is off by 15-20 seconds, your code enters the adjacent time interval 15 seconds prematurely, triggering frequent validation rejections near interval boundaries.
Q. Does this toolbox collect, store, or transmit my keys?
Never. 2FA-Tool.com operates under a zero-trust, privacy-first commitment. All Base32 parsing, key cleaning, URI reverse building, QR code rendering, and NTP offset measurements happen completely inside your browser's local JavaScript memory. No server uploads, no cookies, and no persistent logs.