172.20.72.5 router login

To open the admin panel, type 172.20.72.5 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.72.5 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 is no documented default username and password for 172.20.72.5. Addresses in this part of the private space frequently belong to systems that never had a consumer-style login: a container interface, a hypervisor bridge or a VPN endpoint is reached through the platform that created it, not through a browser form. Where a physical appliance does sit here, the factory credentials for a new unit are printed on its label or given in the model's manual, and in a managed environment they will normally have been replaced during commissioning.

How to log in to your router

  1. Type 172.20.72.5 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.

  2. If the browser reports that it cannot reach 172.20.72.5, 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".

  3. 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

Recovering access here often has nothing to do with a reset button. If the address belongs to a container or virtual network, the correct action is to inspect or recreate that network through the orchestration tooling, and the address may simply be reassigned. If it belongs to a physical appliance, a factory reset erases interface addressing, routes, VPN tunnels, certificates and access rules, which usually means an on-site reconfiguration afterwards. No vendor is documented for this address, so the reset procedure, whether a pinhole, a boot-time key sequence or a console command, has to come from the device's own documentation.

This address falls in 172.16.0.0/12, the middle private range, which runs from 172.16.x.x through 172.31.x.x behind a 255.240.0.0 netmask and holds 1,048,576 addresses. It causes more confusion than the other two ranges, because 172-dot addresses outside those sixteen second octets are ordinary routable public space. 172.20 is inside the private range, so this address is not globally reachable and cannot be traced to any owner, provider or location.

Ranges in this block turn up most in mid-size business networks, lab and test environments, VPN subnets and the bridge networks that container platforms create automatically. Within 172.20.72.0/24 the usable hosts run from 172.20.72.1 to 172.20.72.254, with 172.20.72.255 as the broadcast address. Position 5 sits low in the range, in the region administrators typically reserve for fixed infrastructure rather than DHCP leases, so a server, appliance or virtual interface is a more plausible occupant than a personal device. Only one other address in this particular subnet is separately documented, which makes it a sparsely encountered range.

Most people search for it after finding it on a VPN adapter, a container host or a corporate wireless connection.

Block172.16.0.0/12
Netmask255.240.0.0
Subnet172.20.72.0/24
Usable172.20.72.1 – 172.20.72.254

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.72.0/24

The 172.20.72.0/24 subnet runs from 172.20.72.1 to 172.20.72.254, with 172.20.72.255 reserved as the broadcast address. These are the addresses in it we hold router login details for.

All addresses we cover here

2 addresses in this subnet have a page; the most looked-up are listed here.