MyIP.dogChecking…
Password generator
Create random passwords in your browser. Choose the length and characters you need.
Checking…
Create random passwords in your browser. Choose the length and characters you need.
Checking…
Checking…
Local generation. Nothing is uploaded or saved.
Ready. Nothing is generated until you choose Generate.
Use the password generator with your account’s requirements
This password generator creates random character strings inside your browser after you choose Generate. Start with the default twenty characters, check the destination service's length and character limits, and adjust the controls when necessary. The page does not ask for your username, account address or existing password. You can prepare a new value without telling the tool which account will use it.
Choose a length from eight to 128 characters and a batch size from one to twenty. The password generator includes lowercase letters, uppercase letters, numbers and symbols by default. Open Character rules to change whether every selected group must appear or whether the similar characters I, l, 1, O and 0 should be excluded. These options affect the next generation, not a previously saved account.
Select Generate passwords to display the result. The password generator does not create a secret merely because someone opens or reloads the page. Generate again when you need a fresh batch. Editing any setting removes the previous batch so an old value cannot be mistaken for output created under the new rules. Save a result you intend to use before changing those controls.
A password generator helps you avoid choosing a value based on names, dates or a predictable personal pattern. It does not register that value with an account. Open the destination's genuine password-change flow, enter the new value there, and follow that service's confirmation process. Keep recovery access available while changing credentials so an interrupted change does not leave you guessing which value was accepted.
The password generator's symbol group contains the 32 printable ASCII punctuation characters. With all four groups selected, there are 94 available characters; spaces and non-ASCII characters are outside this tool's alphabet. A site may accept fewer symbols or a lower maximum length. Use the site's published requirements or its validation feedback rather than assuming every generated string will be accepted everywhere.
The password generator can require at least one character from each selected group. This is a compatibility option for accounts that still require such mixtures. Current NIST password guidance tells verifiers not to impose composition rules and specifies a fifteen-character minimum for single-factor passwords. The generator's eight-character lower bound supports constrained cases; it is not a blanket recommendation to use short passwords.
Excluding similar characters removes five explicitly listed characters from the available groups. The password generator does not remove all punctuation, prohibit repeated characters or make the result pronounceable. Use the control when visual transcription matters, and inspect the destination's input carefully. Copying an exact value avoids transcription errors, although the clipboard has its own privacy considerations described below.
Each password generator result is a separate, fixed-length string. The numbered rows are identifiers within this batch; row numbers are not part of the password. A row's Copy button writes only that row's value. With more than one result, Copy all, one per line writes the whole batch separated by newline characters. Do not paste that entire batch into a single account's password field.
The password generator preserves every character it creates. Punctuation is rendered as text rather than markup, and long strings wrap inside the result card without adding characters to the copied value. Hidden results show masking dots while retaining the original value in working memory. Copy continues to copy the original, even while it is hidden; the nearby notice makes that behavior explicit.
After copying from the password generator, save the chosen value in a password manager you trust or another appropriate secure storage method. The generator has no vault, sync service or recovery database. If you clear the page before storing a value, the site cannot retrieve it for you. Test that the changed account accepts the saved credential before discarding the previous recovery context.
The password generator displays the size of the selected alphabet, not an account-security rating. That count says how many different characters are available at each draw. Requiring groups changes which complete strings are eligible. This page therefore avoids turning the count into a misleading universal crack-time estimate; attack conditions and the destination's protections are outside the tool's observations.
The password generator obtains random bytes from the browser's crypto.getRandomValues interface. The Web Cryptography specification defines that cryptographic random-value operation. Our implementation does not substitute a timestamp, a visitor IP, Math.random, or a predictable counter when it is unavailable. A browser error produces an unavailable result, with no fallback password presented as successful.
The password generator uses rejection sampling to map bytes to characters. An alphabet usually does not divide the 256 possible byte values evenly. Directly taking a remainder would favor some characters. Instead, the sampler discards the incomplete upper portion of the byte range, then maps only the evenly divisible portion. Each available character consequently has the same number of accepted byte representations.
When every selected group is required, the password generator samples a complete candidate and checks its groups. Candidates that do not qualify are discarded as a whole. It does not reserve the first positions for uppercase letters or digits, append a mandatory symbol, or patch a missing group into a chosen position. Under the random-source assumption, accepted strings are uniformly selected from the strings that satisfy the chosen rules.
The password generator limits sampling work as well as output size. A batch is returned only when all its requested rows are ready. If the source fails or the retry budget is exhausted, an error replaces the operation instead of exposing a partly completed batch. Those bounds protect page responsiveness; they are not evidence that a browser's random source has passed an independent cryptographic certification.
Independent random draws can repeat characters and, in principle, complete strings. The password generator does not silently remove repeats or promise globally unique credentials. Repeated characters are not automatically evidence of a broken generator. Conversely, a screen full of different-looking strings is not enough to prove random quality. The implementation and its source matter more than a visual impression of randomness.
A password generator should not become a shared credential-distribution system. Batch mode simply saves clicks when you need several candidate values. It does not assign them to people, check previous batches, maintain a global uniqueness registry or notify recipients. Keep the mapping between an account and its chosen value in the system that actually manages those accounts, with suitable access controls.
The password generator keeps its generated strings in the current page component's memory. It does not send them to a generation API, put them in a URL, write them into local or session storage, or include them in a tool analytics event. Normal page assets and the site's ordinary analytics still make network requests. Those requests are separate from generation and do not contain the generated values.
Choose Hide values before showing the screen to someone else. The password generator also hides visible output when the tab becomes hidden. Choose Clear to discard the batch and reset the controls. Leaving the page clears its working state, including the page-cache navigation event. These are application-level behaviors, not a promise to erase every browser-memory copy, operating-system snapshot or extension-accessible value.
Copying from the password generator deliberately places a secret on the system clipboard. Other applications, clipboard history or synchronization features may retain it. Clear does not erase those copies, and this site does not overwrite your clipboard later without another action. Consider your device's clipboard settings and who can access the device before using a generated credential for a sensitive account.
The password generator does not test whether a value appears in a breach database, audit the destination's password storage, identify phishing pages or replace multifactor authentication. A strong random string still needs an appropriate account workflow. For numeric-only requirements, use the separate PIN generator; for connection details, the IP tools directory keeps network observations separate from credential creation.
Once the page and its generation code have loaded, the password generator can create values without contacting a remote generation service. Opening a new page while offline is not guaranteed because this site does not install an offline application cache. Clipboard behavior also depends on browser permissions. Offline generation does not protect against a compromised browser, an installed extension or someone viewing the screen.
The password generator requires an integer length within its range, an integer batch count from one to twenty, and at least one character group. Empty, fractional or oversized entries are rejected. Choose valid settings and run it again. If the message reports unavailable secure randomness, try a current browser rather than accepting a predictable substitute from an unrelated example or error screen.
No. The password generator does not keep a recoverable history. A copied value may remain on your device's clipboard, and a value you saved elsewhere follows that application's retention rules, but the site cannot search those places for you. If you changed an account and lost its credential, follow that account provider's genuine recovery process instead of expecting this page to reconstruct the random draw.
A password generator produces candidate strings, not registered API keys or access grants. An actual API credential also needs server-side issuance, authorization scope, verification, revocation and lifecycle controls. Use the service's own credential-management interface for that purpose. This distinction prevents a locally generated string from being mistaken for a credential that a remote service has agreed to recognize.
The password generator's sampling logic is tested with exhaustive byte-to-index balance checks, all character-group combinations, length boundaries, leading-zero numeric cases and injected random-source failures. Browser checks cover copying, hiding, clearing and local data handling. These checks validate the documented behavior; they do not certify every client device. Source and implementation review: September 28, 2026.