172.20.10.2 router login
To open the admin panel, type 172.20.10.2 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.
172.20.10.2 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 default username and password pair is on record for 172.20.10.2, and none should be inferred from the address itself. A private IP identifies a position on a network, not a product, so any credentials belong to whatever device happens to hold the lease rather than to the number.
Check the printed label on the device, which commonly carries the default login beside the serial number and Wi-Fi key, then the supplied manual, then the support pages of whoever issued the hardware. Equipment provided by an internet or hosting provider often ships with per-unit credentials that are documented only in the account portal or welcome pack.
How to log in to your router
Type 172.20.10.2 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 172.20.10.2, 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
If the sign-in page loads but the password is unknown, exhaust the label, manual and provider account first. Many devices also expose a recovery or password-hint option on the login screen, and some allow an administrator on the same subnet to reset another account.
A factory reset is the last option rather than a quick fix. Because no specific device is known to occupy 172.20.10.2, no reset procedure can be described here with confidence; follow the method in that unit's own documentation. Whatever the method, a reset commonly clears the Wi-Fi name and key, port forwarding, static leases, firewall rules and any provider-specific provisioning, which may then need to be reapplied before the connection works again.
172.20.10.2 belongs to 172.16.0.0/12, the mid-size private range reserved by RFC 1918. With a netmask of 255.240.0.0 it covers 1,048,576 addresses running from 172.16.0.0 to 172.31.255.255, and it is used heavily in mid-size business networks, lab environments, VPN subnets and Docker default bridge networks. This block causes more confusion than the other two private ranges because 172 addresses outside the 172.16 to 172.31 window are ordinary routable public space, so the address looks external at a glance when it is not. Private addresses are not allocated to any organisation and carry no location, ISP or owner; the same address can be in use on thousands of unrelated networks at once.
Within its own segment the address sits in 172.20.10.0/24, where 172.20.10.1 through 172.20.10.254 are usable and 172.20.10.255 is the broadcast address. It is the second address in that range. Administrators commonly reserve the first usable address for the gateway, so .2 more often belongs to a client, server or secondary interface than to the router itself. Twenty-six other addresses in this /24 are separately documented.
Most people arriving here have seen 172.20.10.2 in an IP configuration readout, a DHCP lease list or a connection log, and want to know what device answers on it and how to sign in.
Whois information for 172.16.0.0/12
# 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: 172.16.0.0 - 172.31.255.255
CIDR: 172.16.0.0/12
NetName: PRIVATE-ADDRESS-BBLK-RFC1918-IANA-RESERVED
NetHandle: NET-172-16-0-0-1
Parent: ()
NetType: IANA Special Use
OriginAS:
Organization: Internet Assigned Numbers Authority (IANA)
RegDate: 1994-03-15
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/172.16.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 172.20.10.0/24
The 172.20.10.0/24 subnet runs from 172.20.10.1 to 172.20.10.254, with 172.20.10.255 reserved as the broadcast address. These are the addresses in it we hold router login details for.
All addresses we cover here
27 addresses in this subnet have a page; the most looked-up are listed here.