10.1.1.1 is a private IPv4 address from 10.0.0.0/8, the largest of the three RFC 1918 ranges. With a netmask of 255.0.0.0 the block spans 16,777,216 addresses, none of which are routable across the public internet. Because private space is reusable, the same address can exist simultaneously on thousands of unrelated networks, so 10.1.1.1 has no owner, no registrant, no internet service provider and no geographic location. Whatever answers on it is local to the network you happen to be attached to.
In practice a /8 is never deployed flat. It is subnetted far below its native size, and 10.1.1.1 is most often encountered as part of 10.1.1.0/24, a 256-address segment whose usable hosts run from 10.1.1.1 to 10.1.1.254 with 10.1.1.255 reserved as the broadcast address. 10.1.1.1 is the first usable address in that range, the position administrators and firmware defaults conventionally give to the router or default gateway. That is a convention rather than a rule, and the address can just as legitimately belong to a server, a firewall interface or an ordinary host.
The 10.0.0.0/8 block is common in corporate and campus networks, ISP-managed customer premises equipment, carrier-grade equipment, VPN address pools and container or orchestration networks. Among consumer-facing hardware, the vendors known to ship 10.1.1.1 as a default gateway are Billion, on its BiPAC series, and Telstra, on the Smart Modem. Most people looking this address up want one of three things: to open the administration interface of a modem or router that answers on it, to work out why a browser will not load that interface, or to confirm whether 10.1.1.1 is genuinely the gateway on their current network.
To open the admin panel, type 10.1.1.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. http://10.1.1.1
We hold no reported default credentials for 10.1.1.1. That is not a gap to fill with a guess: no vendor is documented as shipping this address as a factory default, so any list published for it would be invented. The credentials you need belong to whichever device holds this address on your own network.
Where to find them:
No default username and password pair is documented here for 10.1.1.1 specifically, and none should be assumed. The address is used by more than one vendor and by countless private networks, so any single pair quoted for it would be wrong more often than right. Find the credentials that belong to your own hardware instead: check the sticker on the underside or rear panel, the quick-start card in the box, or the vendor's manual for your exact model. ISP-supplied units, including many carrier-branded modems, increasingly ship with a unique per-device password printed on that label rather than a shared factory default, and some publish it in the subscriber account portal.
| Vendor | Models | Username / Password |
|---|---|---|
| Billion | BiPAC series | admin / admin |
| Telstra | Smart Modem | admin / admin |
Both vendors documented on this address, Billion BiPAC units and the Telstra Smart Modem, use a recessed pinhole reset. With the device powered on, press and hold the button with a straightened paperclip until the status lights change and the unit reboots, typically ten to thirty seconds depending on the model.
A factory reset is not free. It clears the Wi-Fi network name and key, any PPPoE or ISP authentication details, port forwards, static DHCP leases, firewall rules and DNS settings, and it restores the LAN addressing to the firmware default. If someone had moved the gateway away from 10.1.1.1, it will revert. ISP-locked units may need re-provisioning by the provider before the connection comes back.
Reset method by vendor:
Type 10.1.1.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 10.1.1.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.
On Windows, run ipconfig /all in Command Prompt and read the Default Gateway line for your active adapter. On Linux, run ip route and look at the address after "default via". On macOS, open System Settings, Network, select the active interface, choose Details and read the Router field under TCP/IP. If that value is not 10.1.1.1, the administration page you want lives at whatever address is shown.
Corporate and commercial VPN clients frequently push a route for the whole of 10.0.0.0/8 into the tunnel, because that is where the office network lives. While connected, traffic to a local 10.1.1.1 is sent to the remote side and never reaches your own hardware. Disconnect the VPN and retry, or check the client for a split-tunnel or local-network-access option.
Many networks default to 192.168.0.0/16 or 172.16.0.0/12 rather than 10.0.0.0/8. If your computer holds an address like 192.168.1.42, nothing on 10.1.1.0/24 is directly reachable, and the browser will simply time out. Check the address your adapter actually received before assuming the router is faulty, and note that a wired and a wireless connection may sit on different segments.
Because 10.0.0.0/8 is so widely used, two devices in the same path can both use it. A modem on 10.1.1.1 sitting behind or in front of a second router that also hands out 10.x addresses produces a double-NAT setup where one interface is unreachable from the wrong side. Connect directly to the device you want to configure, by cable if possible, to rule this out.
Type http://10.1.1.1 explicitly. Browsers that default to HTTPS may fail against firmware that only serves plain HTTP, and firmware that does serve HTTPS usually presents a self-signed certificate, which triggers a warning you have to accept. A minority of devices listen on 8080 or 8443 instead, so http://10.1.1.1:8080 is worth trying before concluding the interface is down.
10.1.1.1 has four fields separated by dots and no letters. Common slips are 10.1.1 with a field missing, 101.1.1.1, and substituting a lowercase L or capital I for the digit 1. Adding www. in front will also fail, since there is no public DNS name. If the browser runs a web search instead of loading a page, the address bar did not accept what was typed.
10.1.1.1 is often mistyped. These all refer to the same address:
l0.l.l.l, 1o.1.1.1, 10.1..1.1, 10 1 1 1, 10.1.1.1..
The most common slip is typing a lower-case letter L in place of the digit 1, or the letter O in place of a zero.
~$ curl https://www.proxydocker.com/api/v2/free/8.8.8.8
{
"ipAddress": "8.8.8.8",
"countryCode": "US",
"countryName": "United States",
"stateProv": "California",
"city": "Mountain View"
}The free API is limited to 500 daily requests and returns city-level location data only. For larger volumes or more data such as latitude/longitude, ISP details and proxy detection, see our commercial offers.
Copyright © 2026 Proxydocker.com, all rights reserved. · Privacy policy · Affiliate program