111.09.150.182 looks like an IPv4 address, but it is not written in the usual dotted-decimal format. The second octet, “09,” contains a leading zero.
If “09” was meant to represent decimal 9, the usual form would be 111.9.150.182. Still, software does not always handle leading zeros in the same way. Some systems reject them, while older or non-standard parsers may read them differently.
This page explains why “09” matters and what public network records show for 111.9.150.182 if that is the intended address.
| Field | Detail |
|---|---|
| Search term | 111.09.150.182 |
| Standard dotted-decimal format | Not as written |
| Main issue | Leading zero in the second octet |
| Possible intended address | 111.9.150.182 |
| Address family if normalized | IPv4 |
| Public or private | Public |
| ASN | AS9808 |
| Network operator | China Mobile Communications Group Co., Ltd. |
| Relevant announced BGP block | 111.9.144.0/20 |
| Registry | APNIC |
| Country association | China |
| Can it identify a person? | No |
What Is 111.09.150.182?
111.09.150.182 has four groups of numbers separated by dots, so it looks like an IPv4 address.
Someone may search for it after finding the value in a server log, firewall record, security alert, analytics report, or another technical source.
The unusual part is “09.” Standard dotted-decimal IPv4 notation does not normally write the value 9 with a zero in front of it. That small difference can matter when software tries to read the address.
Is 111.09.150.182 a Valid IPv4 Address?
Not in standard dotted-decimal notation.
The values 111, 9, 150, and 182 are all within the normal IPv4 range of 0 to 255. The issue is the extra zero before 9.
RFC 3986 defines the grammar used for IPv4 literals in URIs. Under that grammar, a multi-digit octet cannot begin with zero.
If decimal 9 was intended, the normal form is:
111.9.150.182
That does not mean every system will automatically turn 111.09.150.182 into 111.9.150.182. Different parsers may handle the input differently.
Why Does the “09” Matter?
Leading zeros have caused problems in IP parsing because software has not always treated them the same way.
Many modern networking libraries reject IPv4 octets with unnecessary leading zeros. Older software or non-standard parsers may follow different rules.
Some older programming environments treated numbers that begin with zero as octal, or base 8. In octal, the digit 9 is not valid. This means a value such as “09” may be rejected instead of being read as decimal 9.
For that reason, it is better not to assume that every browser, firewall, script, library, or security tool will handle 111.09.150.182 in the same way.
If you mean the decimal address, use 111.9.150.182.
111.09.150.182 vs 111.9.150.182
| Entered value | Standard notation | Leading zero | Safe to assume identical everywhere? | Recommended form |
|---|---|---|---|---|
| 111.09.150.182 | No | Yes | No | 111.9.150.182 if decimal 9 was intended |
| 111.9.150.182 | Yes | No | Yes, as standard dotted-decimal IPv4 | 111.9.150.182 |
If you found 111.09.150.182 in a log or security record, keep the original value for reference.
For a lookup of the possible decimal address, use 111.9.150.182. Before adding a firewall or blocking rule, check how the system that produced the log interpreted the original value.
Network Details for 111.9.150.182
The information below applies to 111.9.150.182. It should not be applied automatically to every possible interpretation of 111.09.150.182.
Network and routing data can change, so these details are a snapshot rather than a permanent record.
For another example of an Asia-based public IPv4 address, see our guide to 183.63.127.22 and its network details.
| Field | Detail |
|---|---|
| IP address | 111.9.150.182 |
| Address type | Public IPv4 |
| ASN | AS9808 |
| Network operator | China Mobile Communications Group Co., Ltd. |
| Relevant announced prefix | 111.9.144.0/20 |
| Registry | APNIC |
| Country association | China |
| Reverse hostname | Not reliably available at the time of checking |
AS9808 is linked to China Mobile Communications Group Co., Ltd. and announces a large amount of IPv4 address space.
Routing can change when an operator moves, splits, or reannounces address ranges. A live BGP lookup is better if you need the exact routing state at a certain time.
Who Owns or Operates 111.9.150.182?
Public IP records can show which organization manages a network. They do not tell you which person is using an address.
IP allocation
Regional Internet Registries allocate IP ranges to organizations. APNIC manages Internet number resources for the Asia-Pacific region.
ASN operator
AS9808 is the autonomous system linked to this address space. Public routing records associate AS9808 with China Mobile Communications Group Co., Ltd.
Network operator
The network operator manages and routes its assigned address space. An IP may be used for network infrastructure, services, or customer connections.
Individual user
Public WHOIS, ASN, and geolocation databases do not reveal who was using 111.9.150.182 at a certain time.
Mobile and broadband providers may also use carrier-grade NAT. This can allow several customers to share one public IP address. Public lookup records alone cannot show whether that was happening for this address at a specific time.
So, the network operator can be identified, but the individual user normally cannot.
Where is 111.9.150.182 Located?
Public network and registry records associate 111.9.150.182 with China at the country level.
More detailed location results should be treated with care. IP geolocation services estimate locations from network records, routing data, infrastructure information, and other signals.
Different databases may return different cities or regions for the same address. Large mobile and broadband networks can also move or reuse addresses across different parts of their network.
An IP address does not reveal a person’s home, street address, or exact physical location.
City-level results from IP lookup tools should be treated as estimates.
Is 111.9.150.182 a Public or Private IP?
111.9.150.182 belongs to public IPv4 address space.
It is outside the private ranges reserved by RFC 1918:
- 10.0.0.0/8
- 172.16.0.0/12
- 192.168.0.0/16
The surrounding address space is announced on the public internet through AS9808.
This does not guarantee that a device or service using 111.9.150.182 can be reached from the internet. Firewalls, NAT, filtering, and other network settings may prevent connections.
Is 111.09.150.182 Dangerous?
An IP address alone cannot tell you whether traffic is harmful.
Finding 111.9.150.182, or the non-standard 111.09.150.182 form, in a log is not enough to label it as malicious.
The activity around the address matters more. Check what was requested, how often requests appeared, whether login attempts failed repeatedly, and whether any security rules were triggered.
A single visit from an address linked to a large network provider is not a warning sign by itself.
IP reputation and blacklist services can add useful context, but their results can change. A flagged result should be compared with your own logs. A clean result does not guarantee that future traffic will be safe.
For a similar IP lookup with a focus on server activity and security checks, read our 111.90.150.204 guide.
Why Might You See This Address in Server Logs?
There are several possible reasons.
Normal website traffic
A normal visitor may have reached your site through an address assigned by the network operator.
Automated crawlers
Bots, monitoring services, scrapers, and other automated tools can make requests from public IP ranges.
Login attempts
Both normal users and automated tools can generate login requests. Repeated failed attempts are more useful evidence than the IP address alone.
API requests
Apps, integrations, or scripts may access an API endpoint and appear in your logs.
Scanning activity
Automated scanners often test large parts of the internet for open services or common security problems. Seeing scanning traffic does not mean your site was specifically targeted.
Shared network traffic
Some providers use shared public addresses. In those cases, more than one device or subscriber may appear behind the same IP.
Incorrectly formatted data
If your logs show 111.09.150.182 instead of 111.9.150.182, the leading zero may have come from another application, imported data, or a formatting issue.
Check how the log was created before deciding what address the system meant.
What Should You Do If You See Suspicious Activity?
Look at the request behavior before blocking anything.
- Check the timestamps and look for repeated activity.
- Review the URLs and endpoints being requested.
- Look for attempts to access login pages or admin areas.
- Check the number of requests made in a short period.
- Review HTTP response codes such as 401, 403, and repeated 404 responses.
- Check authentication logs for failed login attempts.
- Compare user-agent strings and request patterns.
- Use a current IP reputation service as another source of information.
- Apply rate limiting when an endpoint receives abnormal traffic.
- Block an address only when your own logs support that action.
- Keep the original IP value before changing or normalizing it.
Do not assume that one IP always represents one person or one device.
Can an IP Address Identify a Person?
No, not by itself.
An IP lookup can usually show the network that routes an address. It may also give a rough country or region.
It cannot reliably tell you a person’s name, home address, device owner, or who was using the connection at a certain time.
You can also see how network ownership and location data are interpreted in our 124.6.128.20 IP address guide.
Finding a specific subscriber normally requires records held by the internet service provider. Those records are not available through public IP lookup tools.
Frequently Asked Questions
Is 111.09.150.182 the same as 111.9.150.182?
If “09” was intended as decimal 9, 111.9.150.182 is the normal dotted-decimal form. Still, different parsers may reject or read the leading-zero version differently.
Why does the address contain 09?
“09” contains a zero before the digit 9. Standard dotted-decimal IPv4 notation does not normally use leading zeros in an octet.
Is 111.09.150.182 a valid IP address?
It is not written in standard dotted-decimal IPv4 notation. If decimal 9 was intended, the usual form is 111.9.150.182.
Who owns 111.9.150.182?
Public routing records associate the address with AS9808, operated by China Mobile Communications Group Co., Ltd. This identifies the network operator, not an individual user.
Is 111.9.150.182 from China?
Public ASN and registry records associate the address with China. This is a network-level association, not proof of a person’s exact location.
Can this IP reveal someone’s exact location?
No. IP geolocation can provide an estimate, but it cannot reliably reveal an exact street address or physical location.
Is 111.9.150.182 malicious?
The IP address alone is not enough to decide that. Check the traffic pattern, your server logs, and current reputation data.
Should I block this IP?
Only block it if your logs show a clear reason, such as repeated abuse, scanning, excessive requests, or attack attempts.
If your logs contain 111.09.150.182, first check how your system parsed the value before creating a block rule for 111.9.150.182.
Can an IP address identify a person?
No. Public IP records can identify a network and give an approximate geographic association, but they do not identify a specific person.
