Back to Library

Google Dork: inurl:"putty.reg...

Finds exposed PuTTY registry export files containing saved SSH session configurations and connection credentials.

Beginner Friendly
Use with caution
vulnerability

Google Dork Query:

inurl:"putty.reg
0
Not verified

What It Does

This dork uses 'inurl:putty.reg' to locate PuTTY registry export files on web servers. These .reg files contain saved SSH sessions with hostnames, port numbers, usernames, proxy settings, and sometimes stored credentials. They reveal an administrator's complete SSH connection inventory.

Common Use Cases

  • SSH Credential Exposure: Find exposed PuTTY registry files that reveal SSH hostnames, usernames, and saved session configurations.
  • Infrastructure Mapping: Discover SSH connection inventories in PuTTY configs to map an organization's server infrastructure.
  • Credential Hygiene Audit: Check if your PuTTY configuration exports are accidentally published on web-accessible servers.

How to Use Safely

  1. Run the dork in Google to find indexed PuTTY registry files.
  2. Review the .reg file for SSH session hostnames, ports, and username entries.
  3. Map the server infrastructure from the saved SSH connection list.
  4. Report exposed config files and recommend removing them and rotating SSH credentials.

Responsible Use Required

This dork should only be used on systems you own or have explicit authorization to test. Unauthorized access to computer systems is illegal. Always follow ethical guidelines and obtain proper permission before testing.

Related Dorks

Google Dork: Phorum Admin" "Database Connection"...

Locates exposed Phorum forum admin panels that may allow unauthorized access to administrative interfaces or sensitive system configurations.

Find "toshiba Pages

Finds exposed Toshiba network camera login pages that may allow unauthorized access to camera feeds.

Find Welcome to Your New Home Page! Pages

Finds welcome to your new home page! pages revealing default installations that have not been properly configured or secured after deployment.