172.20.3.1 router login
To open the admin panel, type 172.20.3.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.
172.20.3.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.
There are no documented default username and password pairs associated with 172.20.3.1. An IP address is only a way of reaching a device; it does not determine what credentials that device ships with, and any list claiming otherwise for a private address is guesswork. The credentials you need belong to the specific hardware answering at this address on your network.
Look for them on the label or sticker on the underside or rear of the unit, in the printed quick-start guide or the manufacturer's manual for that exact model, or in the documentation supplied by your ISP or network administrator if the equipment was provided to you. On managed or business networks, the defaults have often been changed and only the administrator will have the current details.
How to log in to your router
Type 172.20.3.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 172.20.3.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
If the interface at 172.20.3.1 rejects every login attempt, first confirm you are on the right network and that this address is actually the gateway on your machine, then try any credentials recorded by whoever set the equipment up. No specific vendor is known to ship this address as a default gateway, so the correct reset procedure depends entirely on the hardware in front of you and should be taken from its own manual.
A factory reset is a last resort. On most equipment it erases the configuration: wireless network name and passphrase, port forwarding, static leases, VLANs, VPN settings and any ISP-specific provisioning. Export or photograph the current settings first where the interface allows it, and be prepared to reconfigure the device from scratch afterwards.
172.20.3.1 is a private IPv4 address drawn from the 172.16.0.0/12 range set aside by RFC 1918. That block carries the netmask 255.240.0.0, spans 172.16.x.x through 172.31.x.x and holds 1,048,576 addresses, making it the mid-size option between the single 192.168 class C style block and the very large 10.0.0.0/8 range. Because it is private space, the same address can be in use on countless unrelated networks at the same time, and no registry, owner, carrier or location can be attached to it. The 172.16-172.31 window is also the part of 172.x.x.x that is frequently misread, since 172 addresses outside that window are ordinary routable public space.
In practice this block turns up in mid-size business networks, lab and test environments, VPN subnets and Docker default bridge networking, rather than on consumer equipment straight out of the box.
Within its own segment, 172.20.3.1 sits in the 172.20.3.0/24 subnet, whose usable range runs from 172.20.3.1 to 172.20.3.254 with 172.20.3.255 reserved as the broadcast address. It occupies position 1, the first usable slot, which administrators very commonly assign to the gateway or router interface. Most people looking up this address are trying to reach a management interface on their own network, typically at http://172.20.3.1, in order to check settings, adjust DHCP or diagnose why the page will not load.
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.3.0/24
The 172.20.3.0/24 subnet runs from 172.20.3.1 to 172.20.3.254, with 172.20.3.255 reserved as the broadcast address. These are the addresses in it we hold router login details for.
All addresses we cover here
10 addresses in this subnet have a page; the most looked-up are listed here.