If you searched for 111.90.150.284, you may be trying to identify its location, check its ISP, or understand why an IP lookup tool returns an error. Before investigating further, there is one important detail to know: 111.90.150.284 is not a valid IPv4 address in standard dotted-decimal notation.
The problem is the final number, 284. Each IPv4 octet must fall between 0 and 255. Since 284 exceeds that limit, the complete address cannot represent a standard IPv4 host address.
This guide explains why the address is invalid, whether it can be traced, what might cause it to appear in server logs, and how to troubleshoot the problem without guessing the intended address.
Is 111.90.150.284 a Valid IP Address?
No. The address contains four dot-separated numbers, but its final octet exceeds the permitted range.
According to RFC 3986, the standard IPv4 format consists of four decimal numbers separated by periods, with each number ranging from 0 to 255.
Here is the breakdown of 111.90.150.284:
| Octet | Value | Status |
|---|---|---|
| First | 111 | Valid |
| Second | 90 | Valid |
| Third | 150 | Valid |
| Fourth | 284 | Invalid |
The first three octets meet the numerical requirement. However, the fourth octet exceeds the maximum value of 255.
IPv4 uses a 32-bit address structure divided into four eight-bit octets. Because eight bits can represent values from 0 through 255, a value of 284 cannot fit into one octet.
Therefore, 111.90.150.284 is an invalid IPv4 address as written.
Why Is 284 Outside the Valid IPv4 Range?
Each IPv4 octet contains eight bits. These bits can represent 256 distinct values, beginning at zero and ending at 255.
For example:
111.90.150.200is valid.111.90.150.254is valid.111.90.150.255is within the numerical range, although its network-specific role depends on the subnet.111.90.150.284is invalid.
The difference between 255 and 284 might appear small, but it changes whether the address meets the standard IPv4 format.
A common mistake is to replace 284 with 255 and assume the problem is solved. That creates a different address. There is no evidence that 111.90.150.255 was the intended value.
If you copied the address from a server log, configuration file, or security report, check the original record before making any changes.
For additional technical background, see RFC 791: Internet Protocol, which defines the IPv4 address structure.
Can You Find the Location of 111.90.150.284?
You cannot obtain a reliable host-level location for this string as a valid IPv4 address because the address is malformed.
IP geolocation services use address and network information to estimate a connection’s location. When an address contains an out-of-range octet, a lookup service may reject it, return an error, or handle it in an unexpected way.
If a tool displays a country, city, ISP, or organization for this exact input, verify how the service processed the address before trusting the result.
Do not assume that information about a nearby valid IP address also describes 111.90.150.284. A network range can contain valid addresses without making an out-of-range value valid.
If you need location information, first recover the correct address from the original source. Only then should you investigate its network allocation or geolocation data.
Why Might 111.90.150.284 Appear in Server Logs?
An invalid IP-like string does not automatically indicate a cyberattack. Several issues can cause malformed values to appear in technical records.
1. Typing or copying errors
Someone may have entered an extra digit while recording an address. For example, a valid-looking value might become invalid when an additional digit is appended to the last octet.
2. Application bugs
A website, monitoring tool, or internal application may generate incorrect output because of a programming or data-processing error.
3. Incorrect parsing
An application might extract an address from a larger string incorrectly. The problem may occur when processing API responses, importing logs, or transforming stored data.
4. Database or export problems
A value might become corrupted when records move between systems, spreadsheets, dashboards, or reporting tools.
5. Malformed external input
An application may receive unexpected data from an external source and store it without proper validation.
The most useful clue is whether the problem affects one record or many. A single malformed value may be a transcription error. Repeated invalid values may indicate a validation or processing problem that deserves further investigation.
How to Troubleshoot 111.90.150.284
If this address appears in your application or server logs, follow these steps.
Step 1: Check the Original Record
Locate the raw log entry or original document containing the address. Avoid relying solely on screenshots or manually copied values.
Check nearby entries for context, but do not assume a similar address is the intended correction.
Step 2: Validate Each Octet
Split the address at each period. Confirm that it contains exactly four numerical components and that every component falls between 0 and 255.
For 111.90.150.284, the final component immediately fails validation.
Step 3: Inspect the Data Source
If the address came from your own software, review the code that receives, extracts, or stores IP addresses.
Pay particular attention to input validation, API responses, parsing functions, database records, and log formatting.
Step 4: Review Related Errors
Search for other malformed address strings in the same system. Multiple invalid entries may indicate a shared software issue rather than unrelated typing mistakes.
Step 5: Perform Network Lookups Only After Validation
Commands such as ping, traceroute, and dig serve different networking purposes, but they should not be used to justify a guessed correction.
Once you have confirmed the intended valid address, select the appropriate tool for the investigation. For example, reverse DNS can check whether an address has a corresponding hostname.
Is 111.90.150.284 Dangerous?
The invalid format alone does not establish whether the underlying activity is safe or malicious.
If the string appears in a firewall alert or security report, investigate its origin and examine the surrounding evidence. Look for repeated unauthorized requests, authentication failures, unusual traffic patterns, or application errors.
However, distinguish between an invalid address and a confirmed source of suspicious traffic. The malformed string itself does not identify a real host.
If your application is generating invalid addresses, focus on correcting the validation or data-processing problem. If a security incident is also occurring, investigate that incident using verified records.
This approach avoids unnecessary blocking decisions and prevents incorrect conclusions about a network or its users.
Common Mistakes When Checking Invalid IP Addresses
Assuming four numbers always make a valid IP: An IPv4 address must satisfy the component limits, not just contain four numbers.
Automatically changing 284 to 255: This creates a different address without establishing the original intended value.
Trusting an unexplained geolocation result: A lookup tool may handle malformed input unexpectedly. Validate the input first.
Treating invalid data as proof of an attack: A typo, application bug, or import problem can produce the same symptom.
Using nearby network information as a substitute: Data about a valid address or network range cannot confirm the identity, location, or reputation of an invalid address.
Frequently Asked Questions
What is wrong with 111.90.150.284?
The fourth octet is 284, which exceeds the IPv4 maximum of 255. Therefore, the address is invalid in standard dotted-decimal notation.
Can I perform a WHOIS lookup on 111.90.150.284?
A conventional IP registration lookup requires a valid address. Verify the original value before relying on WHOIS results for network ownership or registration details.
Can an invalid IP address reveal someone’s location?
No reliable host-level location can be established from this malformed address. Correct the input before using geolocation services.
Is 111.90.150.284 a private or public IP?
It cannot be classified as a valid private or public IPv4 host address as written. First, identify the intended valid address.
Why does an IP lookup tool show an error?
The tool may reject the input because its final octet exceeds 255. Other services may process malformed input differently, so an unexpected result should not be treated as verified network information.
How do I fix 111.90.150.284?
Return to the original source and identify the correct value. Do not automatically replace 284 with another number, because the intended address cannot be determined from the malformed string alone.
Final Verdict
111.90.150.284 is not a valid IPv4 address because its fourth octet exceeds 255. The correct response is to validate the original data rather than guess a replacement.
If you encountered this value in a server log, security alert, or application, investigate how it was created and whether other malformed entries exist. Once you have verified the intended address, you can perform meaningful network, location, and security checks.
Accurate validation is the first step toward reliable network troubleshooting.
Related article: 081.63.253.200 IP Lookup: Location, ISP & Security