Default Credentials Scanner

Search 3000+ default credentials for network devices, databases, CMS platforms, IoT, and enterprise software. Cross-references with GitHub security repositories and includes a HIBP breach check for passwords using k-anonymity (only hash prefix sent).

Last updated:

Database: 3000+ default credentials from ihebski/DefaultCreds-cheat-sheet

What are default credentials?

Default credentials are the factory-set usernames and passwords that come pre-configured on network devices, databases, web applications, and IoT equipment. Despite being publicly documented, many systems remain deployed with these defaults unchanged — making them trivially exploitable. This tool aggregates over 3000 known default credential pairs from a community-maintained database, searchable by product name, vendor, or device type.

Key Terminology

k-Anonymity (HIBP)
A privacy-preserving technique used by the Have I Been Pwned password check. Instead of sending your full password hash, only the first 5 characters are sent. The API returns ~500 matching suffixes, and the full comparison happens in your browser. Your actual password never leaves your device.
Credential Stuffing
An attack where breached username/password pairs from one service are automatically tried against other services. Since many people reuse passwords, this is devastatingly effective — which is why checking passwords against breach databases is critical.

🔓 Default Credentials Scanner — Frequently Asked Questions

Why are default credentials dangerous?

Default credentials are the username/password combinations that ship with hardware and software out of the box. Many administrators forget to change them, leaving devices and services accessible to anyone who knows the defaults. Attackers routinely scan for devices running default credentials — it's one of the easiest ways to gain unauthorized access.

Is the HIBP password check safe?

Yes. The tool uses k-anonymity: only the first 5 characters of the SHA-1 hash are sent to the API. The full password never leaves your browser. The API returns all hash suffixes matching that prefix, and the comparison happens locally.