172.30.105.9 router login
To open the admin panel, type 172.30.105.9 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.30.105.9 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 credential pair is recorded for this address, and because the surrounding subnet appears to be privately designed, published defaults are unlikely to apply anyway. Find the device, then find its own defaults on the label attached to it, in its manual, or in the documentation kept by the organisation or provider that deployed it.
How to log in to your router
Type 172.30.105.9 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.30.105.9, 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 login is unknown, treat the administrator as the first line of recovery — internal segments like this are usually managed centrally, and resetting may break connectivity for others. A factory reset clears the working configuration completely, restores the shipped administrative password, and reverts any wireless network name and passphrase to the values printed on the device label.
172.30.105.9 sits in 172.16.0.0/12, the mid-size private range that runs from 172.16.x.x to 172.31.x.x and totals 1,048,576 addresses at netmask 255.240.0.0. Its 172.30 prefix is comfortably inside that reservation, which matters because 172 addresses below 172.16 or above 172.31 are publicly routable and are frequently confused with private ones. Locally, the address belongs to 172.30.105.0/24, with usable hosts from 172.30.105.1 to 172.30.105.254 and broadcast at 172.30.105.255.
Nothing else in this particular /24 has been documented, which is itself telling: the subnet looks like part of a privately planned scheme — a business network, lab segment or VPN allocation — rather than a range shipped by default on consumer equipment. Host 9 is a low but unremarkable slot, unlikely to be the gateway. Most people searching for it are tracing a specific internal device.
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