Buy options
22.82 GBPModel Number | Molto-1-i |
---|---|
Form-factor | pocket calculator format |
Functions | TOTP configurable |
Dimensions | 46x71x4 mm |
Weight | 12 gr |
Programmable | 10 profiles PIN protection feature config protection password |
Product ID | T2-61 |
Wordpress | fully compatible | |
---|---|---|
Google Account | fully compatible | |
Azure On-Prem MFA Server | fully compatible | |
Azure Cloud MFA / Office 365 AD Premium P1 or P2 | fully compatible | |
Azure Cloud MFA / Office 365 AD Free/Basic | fully compatible | |
Stripe Dashboard | fully compatible | |
Meraki Dashboard | fully compatible | |
ISDecisions UserLock | fully compatible | |
ESET Secure Authentication | fully compatible | |
Watchguard AuthPoint | fully compatible | |
Duo | fully compatible | |
AWS | fully compatible | |
Not listed here |
Write us |
|
If the system you are using is not included in the compatibility list, it does not necessarily indicate incompatibility. We encourage you to refer to our integration guides page or get in touch with us for more information. |
Please check product and platform compatibility before placing an order
All pictures shown are for illustration purpose only. Actual product may slightly vary due to product enhancement or other reasons.
Token2 Molto-1-i Multi-profile TOTP hardware token
![](/img/Molto-1Anim1.gif)
Molto-1-i supports long seeds (up to 128 base32 chars) and can be configured with different hash types (sha1 or sha256), time offset (30 seconds or 60 seconds), number of digits (6 or 8 digits) and an optional PIN code protection
Specifications
Dimensions | 46x71x4mm |
TOTP Profiles | up to 10 |
Programmable | via NFC using Windows, iPhone, Android app or cross-platform Python script |
Time sync | Yes |
NFC Access | Password protected - password can be changed |
Time step | 30 or 60 seconds |
OTP Length | 4, 6, 8 or 10 digits |
Maximal seed length | 160 HEX (128 base32) |
Seed hash algorithm | SHA-1 or SHA-256 |
Extra security | PIN protection - OTPs will not show without the correct PIN code entered |
iPhone App guide Python script
FAQ
Q. What is the difference between Molto-1-i and Molto-1 ?
A. Molto-1-i works with Android, Windows and iPhone apps as well as the python script . Molto-1 supports only Windows and Android apps. Additionally, Molto-1-i has PIN protection feature.
Q. How secure is the procedure of programming/seeding the Molto-1-i via NFC?
A. There is absolutely no way to retrieve the seeds anyhow from the device. However, to fully ensure security, in particular, to prevent replay attack by modifying the system time (which is a highly demanded feature to solve the time drift issues) Molto-1 can be protected by setting an NFC access password. New devices will come with a default NFC access password which can be changed immediately. To prevent brute-force attack, the devices will be reset to factory defaults after around 100 unsuccessful NFC access attempts.
Q. What if I have set an NFC access password and forgot it. Does it mean that I can no longer use Molto-1?
A. No, you can still use it by resetting to factory default. This reset will set NFC access password to default, but the operation will also clear all TOTP profiles (seeds and settings).
Q. How long does the battery last?
A. Battery life depends on usage. Burning/programming operations via NFC consume a lot more power, so we must take that into account as well. As a rough estimation, if a token is used a few times per day (i.e. each profile is used once - so 10 button presses a day) and the NFC operations are not very frequent (i.e. not more than once a month) - the Molto-1 token will last for 4-5 years.
Q. Will I lose access to the TOTP profiles when the battery is dead?
A. Yes, but you will have enough time to prepare. Molto-1 will have a battery indicator on the display (). The indicator will show the status throughout the life of the token () . You should replace your token (and migrate the TOTP tokens by resetting the second factor on each respective service) when the indicator shows the battery level as "empty" () - you will still have a couple of months to do this.
Related products
NFC Reader/Writer device for Token2 NFC Burner for Windows and T2F2-NFC FIDO2 Keys
NFC Reader/Writer device for Token2 NFC Burner for Windows and T2F2-NFC FIDO2 Keys
OrderBlog
04-09-2024
Update on EUCLEAK Vulnerability and Chip Security
We want to assure you that we do not use Infineon chips, which are affected by the EUCLEAK side-channel attack recently identified by NinjaLabs. This attack exploits a vulnerability related to the extended Euclidean algorithm (EEA) used in modular inversion.
24-05-2024
Reminder: Our management tools for FIDO2.1 Security Keys are Open Source!
Just a quick reminder: our FIDO2.1 Manager tool, your go-to solution for managing FIDO2 credentials securely, is fully open source! Both the Windows version, created with PowerShell, and a Linux (C++ and Python) version are available.
01-05-2024
FIDO2 Security Keys. To PIN or not to PIN?
Whether to require a PIN when using a FIDO2 security key depends on various factors, including the service provider's authentication settings. This results in situations where some services always prompt for a PIN, while others never do - so we have decided to clarify these aspects.