Does ssid.ai invent a default password when it doesn't know one?

No, and this is the main way it differs from a padded aggregator. Every model carries an explicit credential-type label: static (a documented shared default, shown with its citation), label-unique (unique per device, printed on the label), set-on-setup (no default exists; the router forces you to choose one) or app-only (managed in the vendor's app, no web login). When the honest answer is "there is no shared default", that is what the page says rather than admin/admin.

Where does the MAC address vendor data come from?

The IEEE registries at standards-oui.ieee.org, re-fetched daily at 04:00, so new assignments and reassignments land within a day. All five are ingested: MA-L (24-bit) plus the MA-M, MA-S, IAB and CID sub-block files, and a lookup matches the longest prefix first, so an address inside a block the IEEE subdivided resolves to the company holding it rather than to the registrar. Every API response carries a source field naming the registry, and each vendor page keeps an assignment history of renames and withdrawals that the IEEE's current-state-only registry does not retain.

How current is the data?

All five IEEE registry files (MA-L, MA-M, MA-S, IAB, CID) are re-fetched daily at 04:00. Router pages carry freshness stamps showing when their data was last verified, and each model keeps a verification history of every check, oldest first, with an archived copy of the source page where one exists. The standing target is a median row freshness under 90 days across the dataset.

Can I check ssid.ai's claims independently?

That is the intent of publishing the source URL per field rather than a bare value. Each router page links the manufacturer document behind its credentials; compile runs submit newly-verified source pages to the Wayback Machine at verification time, so "the manufacturer's page said X on this date" is checkable against an archive rather than against ssid.ai's word. The compliance dataset is downloadable as JSON with no auth.

Who operates ssid.ai?

Drumworks Ventures FZ LLC, a free-zone limited liability company registered in the United Arab Emirates. Support is support@ssid.ai; accuracy incidents, security reports and takedown requests go to abuse@ssid.ai.

Trust center

Every router credential on ssid.ai is transcribed from the manufacturer's own published documentation, and each field links to the source document it came from. A credential with no manufacturer citation does not publish, across all 424 tracked models. MAC vendor records come from the IEEE registries (MA-L, MA-M, MA-S, IAB, CID), re-fetched daily at 04:00. Verified accuracy reports are corrected against the manufacturer source within 24 hours.

ssid.ai publishes default-configuration data for network hardware. That is dual-use information, so we hold ourselves to stricter rules than a typical reference site. This page is the standing record of those rules: how data gets in, how it stays fresh, and what happens when something is wrong.

Last updated 2026-08-08 · ssid.ai

Sourcing: official documentation only

Every default-login, gateway-address and reset field in the router directory is transcribed from the manufacturer's own published documentation — user manuals, official support articles, setup guides — and each router page links to the exact source document. Publication is provenance-gated: a credential field with no manufacturer citation does not ship. Forum posts, aggregator lists and word-of-mouth defaults never qualify as sources. Vendor (OUI/MAC) records come from the IEEE registry.

Honest labels, no fabricated defaults

Most credential aggregators pad their pages with “admin / admin” whether or not it was ever true. We don't. Every model carries an explicit credential-type label reflecting what the manufacturer actually documents:

static — a documented shared default, shown with its citation;
label-unique — the password is unique per device, printed on its label;
set-on-setup — no default exists; the router forces you to choose a password at first setup;
app-only— managed through the vendor's app, with no web default login.

When the honest answer is “there is no shared default”, that is what the page says.

Freshness

The IEEE registries (MA-L plus the MA-M, MA-S, IAB and CID sub-blocks) are re-fetched daily at 04:00, so new vendor assignments and reassignments land within a day.
Pages carry freshness stamps showing when their data was last verified.
Standing target: <90 days median row freshness across the dataset.

Responsible use

The directory documents public facts about consumer hardware so that owners can identify devices and get back into equipment they own or administer— after a reset, a move, or inheriting a network nobody documented. Nothing on ssid.ai is specific to any individual's network, and nothing here bypasses a password someone has actually set: a changed admin password makes every default on this site irrelevant. Using this data against networks you are not authorised to administer is prohibited by our terms and by computer-misuse law in essentially every jurisdiction. The durable fix for default credentials is manufacturers shipping unique-per-device passwords — a shift our credType data documents model by model.

Accuracy incidents

A wrong credential row is not a typo — it can lock a legitimate owner out of their next step. We treat credential-accuracy errors as incidents: verified reports are corrected against the manufacturer source within 24 hours, and the fixed page gets a new freshness stamp.

To report an accuracy error, a security concern, or to request a removal:

Email abuse@ssid.ai — the channel for accuracy incidents, security reports and takedown requests; or
use the form on the corrections & takedown page, ideally citing the manufacturer document that shows the correct value.

Data handling

The site runs with no user accounts and a minimal-data posture; the tools that touch secrets (WiFi QR, password generator) run entirely in your browser and carry no analytics. Details in the privacy policy.

FAQ

How trustworthy is ssid.ai's router default-password data?: Every default-login, gateway-address and reset field is transcribed from the manufacturer's own published documentation (a user manual, official support article or setup guide), and each router page links to the exact source document. Publication is provenance-gated: a credential field with no manufacturer citation does not ship. Forum posts, aggregator lists and word-of-mouth defaults never qualify as sources.
Does ssid.ai invent a default password when it doesn't know one?: No, and this is the main way it differs from a padded aggregator. Every model carries an explicit credential-type label: static (a documented shared default, shown with its citation), label-unique (unique per device, printed on the label), set-on-setup (no default exists; the router forces you to choose one) or app-only (managed in the vendor's app, no web login). When the honest answer is "there is no shared default", that is what the page says rather than admin/admin.
Where does the MAC address vendor data come from?: The IEEE registries at standards-oui.ieee.org, re-fetched daily at 04:00, so new assignments and reassignments land within a day. All five are ingested: MA-L (24-bit) plus the MA-M, MA-S, IAB and CID sub-block files, and a lookup matches the longest prefix first, so an address inside a block the IEEE subdivided resolves to the company holding it rather than to the registrar. Every API response carries a source field naming the registry, and each vendor page keeps an assignment history of renames and withdrawals that the IEEE's current-state-only registry does not retain.
What happens if a default password on ssid.ai is wrong?: A wrong credential row is treated as an incident, not a typo, because it can lock a legitimate owner out of their next step. Verified reports are corrected against the manufacturer source within 24 hours and the fixed page gets a new freshness stamp. Report one to abuse@ssid.ai or through the corrections page, ideally citing the manufacturer document showing the correct value.
How current is the data?: All five IEEE registry files (MA-L, MA-M, MA-S, IAB, CID) are re-fetched daily at 04:00. Router pages carry freshness stamps showing when their data was last verified, and each model keeps a verification history of every check, oldest first, with an archived copy of the source page where one exists. The standing target is a median row freshness under 90 days across the dataset.
Can I check ssid.ai's claims independently?: That is the intent of publishing the source URL per field rather than a bare value. Each router page links the manufacturer document behind its credentials; compile runs submit newly-verified source pages to the Wayback Machine at verification time, so "the manufacturer's page said X on this date" is checkable against an archive rather than against ssid.ai's word. The compliance dataset is downloadable as JSON with no auth.
Who operates ssid.ai?: Drumworks Ventures FZ LLC, a free-zone limited liability company registered in the United Arab Emirates. Support is support@ssid.ai; accuracy incidents, security reports and takedown requests go to abuse@ssid.ai.

See the sourcing in practice

Compliance index — 72% of 424 tracked models no longer ship a universal default password, with a free JSON feed
Router default credentials 2026 — the methodology, the open questions, and what we could not verify
Router directory — every model page links the manufacturer document behind its credentials
Pricing — what the data costs, and when a cheaper option is the right call

ssid.ai is operated by Drumworks Ventures FZ LLC, a free-zone limited liability company registered in the United Arab Emirates. Support: support@ssid.ai. Abuse, security and takedown: abuse@ssid.ai.