Steven Adams
Security researcher, authentication specialist, and the person behind all the guides and tools on 2faco.com.
Ryan has spent the better part of a decade working at the intersection of application security and identity systems โ first in security engineering roles at SaaS companies, then independently. His focus is practical: taking authentication standards like TOTP (RFC 6238), FIDO2, and passkeys and translating them into clear, actionable guidance for everyday users and developers alike.
Known online as PhoenixRising90, Steven started his security journey in the early 2010s through CTF competitions and vulnerability research. After watching too many people get locked out of accounts or fall for phishing attacks that a basic 2FA setup would have stopped, he built 2faco.com as a free, privacy-first resource โ browser-based tools that never touch a server, and guides written to explain the why, not just the steps.
Editorial Standards
Every article on 2faco.com is written to be technically accurate, verifiable, and up to date. Where claims are made about security protocols, they are grounded in the relevant RFCs, NIST guidelines, or CISA advisories โ not opinion.
All content is reviewed when standards change, platform UIs are updated, or new attack vectors emerge. Every page displays a "Last reviewed" date โ if it's over 12 months old, it gets checked and updated before anything else.
No affiliate relationships influence the recommendations on this site. When an authenticator app or password manager is recommended, it's because of its security architecture and track record โ not a commission.
RFC-grounded
Technical claims reference IETF RFCs, NIST SP 800-series, or CISA advisories.
Regularly reviewed
Every article carries a last-reviewed date. Security guidance ages โ ours doesn't.
No affiliate bias
Zero affiliate relationships. Recommendations are based on security merit only.
Privacy-first tools
Every tool on this site runs 100% in your browser. Nothing is ever sent to a server.
Selected Articles
Get in Touch
Have a correction, a topic suggestion, or a security question? The best way to reach Ryan is through the contact page. Factual corrections are taken seriously and acted on quickly โ accurate security information matters.