Free HOTP QR Code Generator
Build standard otpauth://hotp/ QR codes for counter-based authenticator apps and hardware tokens. Pure RFC 4226, no server, no signup.
- QR Generator
- 명함 디자이너
- WiFi 카드 인쇄
- 일괄 CSV (500개 코드)
- 40개 템플릿
- 20개 언어
이 바코드 형식은 전경색과 배경색만 사용하여 단색으로 렌더링됩니다. 템플릿, 점/눈 모양, 그라디언트, 프레임, 중앙 로고는 QR 코드에만 적용되며 여기서는 숨겨집니다.
템플릿 30개 더 보기
위의 버튼을 사용하여 스타일을 저장하여 즐겨찾기를 여기에 저장하세요.
또는 내장 아이콘 선택:
108개 아이콘 더 보기
QR 뒤에 낮은 불투명도로 표시됩니다. 사진을 통해서도 스캔되도록 EC=H를 자동 적용합니다.
일괄 생성
CSV를 업로드하여 한 번의 배치로 최대 500개의 QR 코드를 생성하세요. 각 행은 고유한 QR이 되며, 템플릿을 선택하거나 행별로 21가지 속성(색상, 프레임, 도트/아이/아이볼 스타일, 그라디언트, 투명도, 크기, 오류 정정, 형식, 내장 로고 등)을 재정의할 수 있습니다.
21개 열: type, data, filename, frametext, frame, template, fgcolor, bgcolor, size, ec, dotstyle, eyestyle, format, logo, gradient, g2, gtype, gangle, transparent, eyeball, eyecolor. type과 data만 필수입니다. data 내의 필드를 구분하려면 |을 사용하세요(예: ssid|password|WPA).
URL, WiFi, vCard, MeCard, Email, SMS, Event, Location, UPI, SEPA, PayPal, Crypto, Micro QR, rMQR을 포함한 20가지 QR 유형을 모두 지원합니다. 샘플 CSV를 다운로드하여 모든 열, 40개 템플릿, 11개 프레임 스타일, 12개의 내장 로고를 확인해 보세요.
1. 샘플 CSV 다운로드 · 2. Google Sheets, Excel, Numbers 또는 텍스트 에디터에서 편집 · 3. 여기에 업로드
QR 전체 – 유형, 모든 필드 값, 스타일, 프레임, 로고, 명함 디자인 –을 단일 .qr.json 파일로 저장합니다. 나중에 로드하여 한 번의 클릭으로 모든 것을 재현합니다.
QR 코드를 생성하려면 내용을 입력하세요
법정에서도 유효한 전자서명
Abundera Sign은 기본 전자서명을 넘어섭니다. 모든 문서에 암호화 증명, 독립 검증, 변조 방지 증거 패키지가 포함됩니다.
- 자동 생성되는 법원 준비 증거 패키지
- 개인 문서 봉인 — 즉시 변조 감지
- 5개의 독립 시스템에 고정 — 단일 장애 지점 없음
How HOTP Differs from TOTP
HOTP and TOTP both produce 6- to 8-digit one-time codes from a shared Base32 secret, and both use the same otpauth:// URI scheme. The single difference: TOTP advances the code on time (typically every 30 seconds), while HOTP advances on a counter that the client increments each time it generates a code. The server tracks the same counter and accepts codes within a small look-ahead window.
HOTP is the right choice when you can't trust the device clock, when the device has no clock (hardware tokens), or when codes need to remain valid until they are used (login flows where typing time matters). The trade-off is that the counter can drift if the user generates codes without submitting them — most servers handle this with a re-sync window of 10 to 50 codes.
Where HOTP shines
- YubiKey OTP slot — the original use case. Press the button, the YubiKey emits the next HOTP code as keystrokes.
- Hardware tokens — Feitian c100, RSA SecurID 700-series, programmable tokens from Token2 and Protectimus. All ship with HOTP firmware.
- Air-gapped systems — submarines, remote sensors, factory-floor terminals where time sync is unreliable but a counter is durable.
- Server-side OTP backup — single-use recovery codes are HOTP under the hood, with the counter incremented per use.
Fields explained
- Issuer — service name (e.g. GitHub). Shown as the heading in the authenticator app.
- Account — usually your username or email. Shown as the subheading.
- Secret — Base32-encoded shared secret. 16, 26, or 32 characters typically.
- Algorithm — SHA1 (default), SHA256, or SHA512.
- Digits — 6 (default) or 8.
- Initial counter — usually 0. Set to a higher value if re-provisioning a token that has already been used.
Privacy
The shared secret is sensitive. Abundera QR runs entirely in your browser — the secret never touches a server, never gets logged, never leaves your device. Generate on an offline laptop for maximum paranoia.
26개 언어 지원
완전히 번역된 UI, 원어 스크립트 렌더링, 아랍어 및 우르두어 우→좌 지원.
Frequently Asked Questions
Which apps and tokens can read these HOTP QR codes?
Any standards-compliant HOTP implementation: Aegis, Raivo, FreeOTP, FreeOTP+, KeePassXC, Yubico Authenticator, Token2 personalization tools, Protectimus desktop tools, and most modern enterprise IAM platforms (Okta, Auth0, Keycloak). Note: Google Authenticator quietly ignores the counter parameter and treats everything as TOTP — pick a different app for HOTP setups.
How is HOTP different from a YubiKey FIDO2 / WebAuthn key?
Different protocol entirely. HOTP is a shared-secret one-time-code scheme (RFC 4226). FIDO2/WebAuthn is asymmetric public-key authentication. Both are 'second factors' but FIDO2 is phishing-resistant where HOTP is not. HOTP is a fit when the relying party only supports OTP, or when you specifically need a code that can be typed.
What happens if the counter drifts out of sync?
Most servers accept codes within a look-ahead window (typically 10 codes) and resync the counter when a valid forward code arrives. If drift exceeds the window the user has to re-enroll. Some IAM platforms expose a 'resync' admin action that takes two consecutive codes to recompute the offset.
Why does Google Authenticator give wrong codes for HOTP QRs?
Google Authenticator treats every otpauth:// QR as TOTP regardless of the path. The codes it produces are valid TOTP codes against your secret — not HOTP codes — so the server rejects them. Use Aegis, Raivo, Yubico Authenticator, or a hardware token instead.
Can I program a YubiKey OTP slot from this QR?
Not directly. YubiKey OTP slots are programmed with the YubiKey Manager (GUI) or ykman (CLI). You can copy the Base32 secret from the form into ykman: ykman oath accounts add --type HOTP --algorithm SHA1 --digits 6 ISSUER:ACCOUNT <secret>.
What's the maximum counter value?
RFC 4226 allows counters up to 2^63 - 1. Practically, most implementations cap it lower (32-bit on legacy hardware). Hundreds of thousands of presses is fine on any modern token.
Should I use HOTP or TOTP for new deployments?
TOTP for almost everything. HOTP is the right pick only for: hardware tokens that lack a clock, deeply air-gapped environments, or single-use recovery codes. For phone-based 2FA, time-based codes are the standard and the user experience is significantly better.