10.100.100.1 router login
To open the admin panel, type 10.100.100.1 into your browser's address bar. If the page does not load, this is probably not the gateway address on your network — see the checks below.
10.100.100.1 router passwords
Where to find them:
- The label on the underside or back of the router — most manufacturers print the default admin username, password and Wi-Fi key there.
- The quick-start card or manual that came in the box.
- Your ISP's account portal, if the device was supplied by them — many set a unique password per line rather than a shared default.
No factory username and password is documented for this address. A gateway position tells you where a device sits, not who made it or what it ships with, so any pair quoted for the number itself would be fiction. The device's own defaults, if it still uses them, appear on its label or in its documentation, and some equipment forces a password to be set on first boot instead of shipping one. On a guest, lab or management segment the gateway is usually administered by someone else, and their credentials are the ones that work.
How to log in to your router
Type 10.100.100.1 into your browser's address bar and press Enter. Type it by hand rather than accepting an autocomplete suggestion, which often fills in a different address you visited before.
If the browser reports that it cannot reach 10.100.100.1, this is not the gateway address on your network. On Windows run ipconfig /all and read the Default Gateway line; on macOS open System Settings, Network, Details, TCP/IP; on Linux run ip route and read the address after "default via".
If the login page loads but rejects your credentials, and you have never changed them, use the defaults printed on the device's label. If they have been changed and nobody knows the new password, a factory reset is the only way back in.
If you do not know the password
Since no vendor is tied to this address, use the reset method documented for the actual hardware. The common form is a recessed button held while the unit is powered, but hold times and behaviour vary, and some devices need a console cable or a bootloader recovery mode instead. Consider what a reset destroys: on a gateway it removes routing and NAT rules, DHCP scopes, firewall policy, VPN configuration and wireless settings, and every client on the segment loses connectivity until it is rebuilt. Take a configuration backup first and, on shared infrastructure, get agreement before you interrupt it.
This address is drawn from 10.0.0.0/8, the private block described by RFC 1918. Under a 255.0.0.0 mask it holds 16,777,216 addresses, the largest of the reserved ranges, and it is standard in corporate and campus networks, ISP-managed CPE, carrier-grade platforms, VPN address pools and container networking. In practice nobody deploys a /8 flat; it is subdivided many times over before hosts appear.
One of those subdivisions is 10.100.100.0/24, where usable addresses stretch from 10.100.100.1 to 10.100.100.254 and 10.100.100.255 carries broadcast traffic. The address in question is the first of those, the slot that by long habit holds the gateway interface of the segment. The mirrored 100.100 pattern is a mnemonic choice made by whoever designed the plan, typical of secondary segments such as guest wireless, a lab, a management network or the inside of a VPN tunnel, rather than anything a device arrives configured with.
Some 233 people a year search for it. Nearly all have found it as the default gateway on a connected client and want to reach whatever administers the segment. This /24 also looks busy: thirteen other addresses in it are documented here, which is consistent with a segment in regular use rather than a leftover.
Whois information for 10.0.0.0/8
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2024, American Registry for Internet Numbers, Ltd.
#
NetRange: 10.0.0.0 - 10.255.255.255
CIDR: 10.0.0.0/8
NetName: PRIVATE-ADDRESS-ABLK-RFC1918-IANA-RESERVED
NetHandle: NET-10-0-0-0-1
Parent: ()
NetType: IANA Special Use
OriginAS:
Organization: Internet Assigned Numbers Authority (IANA)
RegDate: 1995-06-23
Updated: 2013-08-30
Comment: These addresses are in use by many millions of independently operated networks, which might be as small as a single computer connected to a home gateway, and are automatically configured in hundreds of millions of devices. They are only intended for use within a private context and traffic that needs to cross the Internet will need to use a different, unique address.
Comment:
Comment: These addresses can be used by anyone without any need to coordinate with IANA or an Internet registry. The traffic from these addresses does not come from ICANN or IANA. We are not the source of activity you may see on logs or in e-mail records. Please refer to http://www.iana.org/abuse/answers
Comment:
Comment: These addresses were assigned by the IETF, the organization that develops Internet protocols, in the Best Current Practice document, RFC 1918 which can be found at:
Comment: http://datatracker.ietf.org/doc/rfc1918
Ref: https://rdap.arin.net/registry/ip/10.0.0.0
OrgName: Internet Assigned Numbers Authority
OrgId: IANA
Address: 12025 Waterfront Drive
Address: Suite 300
City: Los Angeles
StateProv: CA
PostalCode: 90094
Country: US
RegDate:
Updated: 2012-08-31
Ref: https://rdap.arin.net/registry/entity/IANA
OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName: ICANN
OrgAbusePhone: +1-310-301-5820
OrgAbuseEmail: abuse@iana.org
OrgAbuseRef: https://rdap.arin.net/registry/entity/IANA-IP-ARIN
OrgTechHandle: IANA-IP-ARIN
OrgTechName: ICANN
OrgTechPhone: +1-310-301-5820
OrgTechEmail: abuse@iana.org
OrgTechRef: https://rdap.arin.net/registry/entity/IANA-IP-ARIN
Other documented addresses in 10.100.100.0/24
The 10.100.100.0/24 subnet runs from 10.100.100.1 to 10.100.100.254, with 10.100.100.255 reserved as the broadcast address. These are the addresses in it we hold router login details for.
All addresses we cover here
14 addresses in this subnet have a page; the most looked-up are listed here.