Client Keystore Recovery — Frequently Asked Questions

What exactly is a “keystore JSON”?

A password-encrypted JSON file (name starts with UTC--) that stores your Ethereum private key (Scrypt/PBKDF + AES). We attempt to recover the password; keys remain encrypted until unlocked.

My paths look different. Is that a problem?

No. Data directories are configurable. If in doubt, include the entire client data directory—we’ll locate the keystore/ or keys/ subfolder.

I have multiple UTC-- files. Which one?

Send them all. We’ll identify which file matches the address you provide.

Do you need my seed phrase or private key?

No. For assessment we only need the encrypted keystore JSON and your password hints. Never share your seed phrase or private key.

Is recovery guaranteed?

No. Success depends on password complexity and hint quality. We start with a free offline assessment and then provide realistic next steps.

Ready for a Free Assessment?

Send your Ethereum keystore JSONs securely. Our team will review them offline and get back with options—no commitment, no risk.

Start Recovery

Password Hints Guide (What Helps Most)

Length (exact or range): “8–10”, “12 exactly”.
Character sets: lower/UPPER, digits, symbols (which?).
Patterns: Word+year, capitalized word + 2 digits, starts with initials, ends with 88 or !, etc.
Words you reuse: names, brands, pets, places, fandoms.
Dates/numbers: birthdays, anniversaries; formats used (DDMMYYYY, YYYY, etc.).
Typical endings: !, !!, 123, 2020, etc.
Language/keyboard: non-English letters, QWERTZ/QWERTY habits, frequently used symbols.

Even small details can massively reduce the keyspace—saving time and improving success odds.

Independent Assessment: Please consider this as an independent assessment of your recovery problem. Submitting your case does not commit you to any service or payment.

Privacy: Your files are handled confidentially and are not shared with third parties. We only use them to evaluate your recovery request.

Ready for a Free Assessment?

Send your Ethereum keystore JSONs securely. Our team will review them offline and get back with options—no commitment, no risk.

Start Recovery

How to Prepare & Send Files (Secure)

Copy your UTC-- keystore file(s) (or the whole keystore//keys/ folder) to your Desktop.
Compress into .zip or .7z and set a temporary password for the archive.
Submit an inquiry on our inquiry page. We’ll reply with a one-time, secure upload link for your encrypted archive. Please do not email files.
Add detailed password hints (see below). Better hints dramatically improve success odds and allow a realistic time estimate.

Offline only: All assessments and cracking runs are performed on isolated systems. First step is an independent assessment—no commitment required.

Password Hints Guide (What Helps Most)

Length (exact or range): “8–10”, “12 exactly”.
Character sets: lower/UPPER, digits, symbols (which?).
Patterns: Word+year, capitalized word + 2 digits, starts with initials, ends with 88 or !, etc.
Words you reuse: names, brands, pets, places, fandoms.
Dates/numbers: birthdays, anniversaries; formats used (DDMMYYYY, YYYY, etc.).
Typical endings: !, !!, 123, 2020, etc.
Language/keyboard: non-English letters, QWERTZ/QWERTY habits, frequently used symbols.

Even small details can massively reduce the keyspace—saving time and improving success odds.

Independent Assessment: Please consider this as an independent assessment of your recovery problem. Submitting your case does not commit you to any service or payment.

Privacy: Your files are handled confidentially and are not shared with third parties. We only use them to evaluate your recovery request.

Ready for a Free Assessment?

Send your Ethereum keystore JSONs securely. Our team will review them offline and get back with options—no commitment, no risk.

Start Recovery

What We Need

Your Ethereum keystore JSON file(s) (typically named UTC--YYYY-MM-DD...--<address>).
Password hints (see checklist below).
(Optional) The public address and approximate year/app/client you created it with.

We do not need your seed phrase or plaintext private key for assessment. Never share them.

Where to Find Your Keystores

Tip: If paths differ on your setup, include the entire data directory for your client—there’s usually a keystore/ or keys/ subfolder with UTC-- files.

Nethermind

Linux/macOS (common default): ~/.nethermind/keystore/
Windows (common default): within the Nethermind data directory → keystore\

Besu (Hyperledger Besu)

Linux/macOS (default data-dir): ~/.besu/keystore/
Windows (default data-dir): in your Besu data directory → keystore\

Parity / OpenEthereum

Linux: ~/.local/share/io.parity.ethereum/keys/ (or ~/.local/share/openethereum/keys/)
macOS: ~/Library/Application Support/io.parity.ethereum/keys/ (or ~/Library/Application Support/openethereum/keys/)
Windows: in the Parity/OpenEthereum data directory → keys\

If you used multiple accounts, include all your UTC-- files—we’ll match them to your address.

How to Prepare & Send Files (Secure)

Copy your UTC-- keystore file(s) (or the whole keystore//keys/ folder) to your Desktop.
Compress into .zip or .7z and set a temporary password for the archive.
Submit an inquiry on our inquiry page. We’ll reply with a one-time, secure upload link for your encrypted archive. Please do not email files.
Add detailed password hints (see below). Better hints dramatically improve success odds and allow a realistic time estimate.

Offline only: All assessments and cracking runs are performed on isolated systems. First step is an independent assessment—no commitment required.

Password Hints Guide (What Helps Most)

Length (exact or range): “8–10”, “12 exactly”.
Character sets: lower/UPPER, digits, symbols (which?).
Patterns: Word+year, capitalized word + 2 digits, starts with initials, ends with 88 or !, etc.
Words you reuse: names, brands, pets, places, fandoms.
Dates/numbers: birthdays, anniversaries; formats used (DDMMYYYY, YYYY, etc.).
Typical endings: !, !!, 123, 2020, etc.
Language/keyboard: non-English letters, QWERTZ/QWERTY habits, frequently used symbols.

Even small details can massively reduce the keyspace—saving time and improving success odds.

Independent Assessment: Please consider this as an independent assessment of your recovery problem. Submitting your case does not commit you to any service or payment.

Privacy: Your files are handled confidentially and are not shared with third parties. We only use them to evaluate your recovery request.

Ready for a Free Assessment?

Send your Ethereum keystore JSONs securely. Our team will review them offline and get back with options—no commitment, no risk.

Start Recovery

What We Need

Your Ethereum keystore JSON file(s) (typically named UTC--YYYY-MM-DD...--<address>).
Password hints (see checklist below).
(Optional) The public address and approximate year/app/client you created it with.

We do not need your seed phrase or plaintext private key for assessment. Never share them.

Where to Find Your Keystores

Tip: If paths differ on your setup, include the entire data directory for your client—there’s usually a keystore/ or keys/ subfolder with UTC-- files.

Nethermind

Linux/macOS (common default): ~/.nethermind/keystore/
Windows (common default): within the Nethermind data directory → keystore\

Besu (Hyperledger Besu)

Linux/macOS (default data-dir): ~/.besu/keystore/
Windows (default data-dir): in your Besu data directory → keystore\

Parity / OpenEthereum

Linux: ~/.local/share/io.parity.ethereum/keys/ (or ~/.local/share/openethereum/keys/)
macOS: ~/Library/Application Support/io.parity.ethereum/keys/ (or ~/Library/Application Support/openethereum/keys/)
Windows: in the Parity/OpenEthereum data directory → keys\

If you used multiple accounts, include all your UTC-- files—we’ll match them to your address.

How to Prepare & Send Files (Secure)

Copy your UTC-- keystore file(s) (or the whole keystore//keys/ folder) to your Desktop.
Compress into .zip or .7z and set a temporary password for the archive.
Submit an inquiry on our inquiry page. We’ll reply with a one-time, secure upload link for your encrypted archive. Please do not email files.
Add detailed password hints (see below). Better hints dramatically improve success odds and allow a realistic time estimate.

Offline only: All assessments and cracking runs are performed on isolated systems. First step is an independent assessment—no commitment required.

Password Hints Guide (What Helps Most)

Length (exact or range): “8–10”, “12 exactly”.
Character sets: lower/UPPER, digits, symbols (which?).
Patterns: Word+year, capitalized word + 2 digits, starts with initials, ends with 88 or !, etc.
Words you reuse: names, brands, pets, places, fandoms.
Dates/numbers: birthdays, anniversaries; formats used (DDMMYYYY, YYYY, etc.).
Typical endings: !, !!, 123, 2020, etc.
Language/keyboard: non-English letters, QWERTZ/QWERTY habits, frequently used symbols.

Even small details can massively reduce the keyspace—saving time and improving success odds.

Independent Assessment: Please consider this as an independent assessment of your recovery problem. Submitting your case does not commit you to any service or payment.

Privacy: Your files are handled confidentially and are not shared with third parties. We only use them to evaluate your recovery request.

Ready for a Free Assessment?

Send your Ethereum keystore JSONs securely. Our team will review them offline and get back with options—no commitment, no risk.

Start Recovery

Nethermind / Besu / Parity (OpenEthereum) Keystore Recovery – How to Prepare Your Files

Q: What exactly is a “keystore JSON”?

A password-encrypted JSON file (name starts with UTC--) that stores your Ethereum private key (Scrypt/PBKDF + AES). We attempt to recover the password; keys remain encrypted until unlocked.

Have Ethereum keystore JSON files (names start with UTC--) from Nethermind, Besu, or Parity/OpenEthereum but forgot the password? We perform secure, offline recovery assessments of encrypted keystores. Follow the steps below to prepare your files and request a free, no-obligation assessment.

Request Free Assessment

See All Supported Wallets

What We Need

Your Ethereum keystore JSON file(s) (typically named UTC--YYYY-MM-DD...--<address>).
Password hints (see checklist below).
(Optional) The public address and approximate year/app/client you created it with.

We do not need your seed phrase or plaintext private key for assessment. Never share them.

Where to Find Your Keystores

Tip: If paths differ on your setup, include the entire data directory for your client—there’s usually a keystore/ or keys/ subfolder with UTC-- files.

Nethermind

Linux/macOS (common default): ~/.nethermind/keystore/
Windows (common default): within the Nethermind data directory → keystore\

Besu (Hyperledger Besu)

Linux/macOS (default data-dir): ~/.besu/keystore/
Windows (default data-dir): in your Besu data directory → keystore\

Parity / OpenEthereum

Linux: ~/.local/share/io.parity.ethereum/keys/ (or ~/.local/share/openethereum/keys/)
macOS: ~/Library/Application Support/io.parity.ethereum/keys/ (or ~/Library/Application Support/openethereum/keys/)
Windows: in the Parity/OpenEthereum data directory → keys\

If you used multiple accounts, include all your UTC-- files—we’ll match them to your address.

How to Prepare & Send Files (Secure)

Copy your UTC-- keystore file(s) (or the whole keystore//keys/ folder) to your Desktop.
Compress into .zip or .7z and set a temporary password for the archive.
Submit an inquiry on our inquiry page. We’ll reply with a one-time, secure upload link for your encrypted archive. Please do not email files.
Add detailed password hints (see below). Better hints dramatically improve success odds and allow a realistic time estimate.

Offline only: All assessments and cracking runs are performed on isolated systems. First step is an independent assessment—no commitment required.

Password Hints Guide (What Helps Most)

Length (exact or range): “8–10”, “12 exactly”.
Character sets: lower/UPPER, digits, symbols (which?).
Patterns: Word+year, capitalized word + 2 digits, starts with initials, ends with 88 or !, etc.
Words you reuse: names, brands, pets, places, fandoms.
Dates/numbers: birthdays, anniversaries; formats used (DDMMYYYY, YYYY, etc.).
Typical endings: !, !!, 123, 2020, etc.
Language/keyboard: non-English letters, QWERTZ/QWERTY habits, frequently used symbols.

Even small details can massively reduce the keyspace—saving time and improving success odds.

Independent Assessment: Please consider this as an independent assessment of your recovery problem. Submitting your case does not commit you to any service or payment.

Privacy: Your files are handled confidentially and are not shared with third parties. We only use them to evaluate your recovery request.

Ready for a Free Assessment?

Send your Ethereum keystore JSONs securely. Our team will review them offline and get back with options—no commitment, no risk.

Start Recovery