Information

About

Gabor Kohanyi operates, develops, publishes, edits and reviews RandomStrongPasswordGenerator.com personally.

Web projects since 2003

I have built and operated my own web projects since 2003. My work combines web development, online publishing, SEO, data-driven websites, automation and AI-assisted workflows. I focus on practical services that people can use directly, with clear limitations and maintainable infrastructure.

RandomStrongPasswordGenerator.com is one of my personal projects.

Professional background

For more than two decades, I have built and operated independent web businesses at the intersection of software, online publishing, search visibility, automation and useful data. My work turns technically complex ideas into clear, dependable services that people can use directly, from focused browser tools to content-rich information platforms. I value practical results, transparent limitations and products designed for long-term usefulness rather than short-lived trends.

Learn more about my work on kohanyi.hu and connect with me on LinkedIn.

Role on this website

I am responsible for the site architecture, tools, publishing, editorial direction, source selection, review and corrections. I designed the service so the public articles and the browser area that handles generated or entered secrets remain separate.

I check the tools through repeatable technical and browser-based verification. This work is not presented as a formal penetration test or independent security audit.

Why the tools use an isolated origin

Password tools should minimize the number of systems that can encounter a secret. The public pages may use analytics and advertising with the appropriate Google consent notice, while the secure tool area contains none of those services and does not send secret values to the server.

The architecture reduces exposure but cannot protect a compromised device, malicious extension, unsafe clipboard or phishing page. Those limits are documented in the Security and Privacy Methodology.

Research and source standards

I prefer primary technical sources, including NIST authentication guidance, OWASP cheat sheets, FIDO and W3C standards, CISA material and official platform documentation. A vendor’s current account interface remains authoritative for its accepted password characters and available sign-in methods.

Older articles are not treated as proof that a claim remains current. Guidance is reviewed against current sources, and corrections are made when the evidence changes.

AI-assisted work and human responsibility

AI may assist research, drafting, editing, code development and test creation. It is not treated as a factual source. I remain responsible for what is published, compare important claims with primary sources, and avoid inventing credentials, tests, statistics or experience.

The Editorial Policy explains sourcing, updates, corrections and external-link selection.

Expertise boundaries

My authority here comes from long-term practical web development and publishing, transparent methods, source review and responsibility for the implementation. I do not claim a cybersecurity certification, cryptography degree, academic security qualification, formal penetration-testing credential or security-researcher status.

Tool output and articles are educational. Organizations with regulated or high-risk systems should use qualified security and legal professionals.

Corrections and contact

I review reproducible technical reports and well-sourced editorial corrections. Use the Contact page, identify the exact page and claim, and provide a primary source where possible. Do not send passwords, backup codes, session tokens or personal data that is not needed.

Technical reports are compared with the current public tool behavior. Editorial reports are checked against the cited source and its full context before a correction is published.