172.20.12.10 router login
To open the admin panel, type 172.20.12.10 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.12.10 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 recorded for 172.20.12.10, and none can honestly be inferred. Private space is reusable by anyone, so whatever listens on this address was chosen by whoever built the network rather than by any convention.
The reliable source is the device itself. Check the printed label on its underside or rear panel, the quick-start card that shipped in the box, and the manual for that exact model number. If the equipment belongs to an employer, a landlord or a service provider, the credentials are commonly held in their documentation or by whoever provisioned it, and are frequently changed from factory values during setup.
How to log in to your router
Type 172.20.12.10 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.12.10, 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
A factory reset is a genuine loss, not a formality. It clears static addressing, VLAN assignments, firewall and port-forwarding rules, wireless keys and any account created during setup, and every client that trusted the old configuration must be reconfigured.
There is a further catch at this position. A device holding 172.20.12.10 is likely statically configured, and a reset commonly returns it to a factory default address in some other range, so the address you came here for may simply stop responding. Export a configuration backup first if the interface offers one. Since no vendor is known to ship this address, follow the reset procedure printed in that unit's own manual, which typically involves a recessed button held while the device is powered.
The address 172.20.12.10 falls inside 172.16.0.0/12, the mid-size private range set aside by RFC 1918. With a netmask of 255.240.0.0 the block spans 1,048,576 addresses from 172.16.0.0 to 172.31.255.255, and it turns up most often in mid-size business networks, lab environments, VPN subnets and Docker default bridge networks. It also causes more confusion than the other private ranges, because 172.x.x.x values outside 172.16 through 172.31 are ordinary public space that routes on the internet.
This particular address sits in the subnet 172.20.12.0/24, where usable hosts run from 172.20.12.1 to 172.20.12.254 and 172.20.12.255 is reserved for broadcast. Host number 10 is a low position but not the .1 slot conventionally handed to a gateway. Addresses this low usually sit below where a DHCP server begins issuing leases, so they tend to be assigned deliberately: a server, a printer, an access point, a camera or a reserved lease. Five other addresses in this /24 are documented here, so the subnet is in use but only sparsely observed.
Most visitors have read this address off a client list, an ARP table or a configuration screen and want to know what answers on it. Only a machine on that same network can reach it.
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.12.0/24
The 172.20.12.0/24 subnet runs from 172.20.12.1 to 172.20.12.254, with 172.20.12.255 reserved as the broadcast address. These are the addresses in it we hold router login details for.
All addresses we cover here
6 addresses in this subnet have a page; the most looked-up are listed here.