> ## Content Index
> Fetch the complete content index at: https://routerhaven.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# IP address classes explained: A, B, and C
- URL: https://routerhaven.com/ip-address-classes-a-b-c/
- Published: 2026-11-18T04:50:00.000Z
- Updated: 2026-11-18T04:50:00.000Z
- Author: Caleb Renwick
- Tags: Networking

IP address classes were an older way to divide IPv4 space into a network part and a host part. Class A covers first octet 0 to 127 with a default mask of 255.0.0.0, or /8\. Class B covers first octet 128 to 191 with a default mask of 255.255.0.0, or /16\. Class C covers first octet 192 to 223 with a default mask of 255.255.255.0, or /24\. Those fixed default masks are how the class split the network and host parts, so the class told you how much of the address identified the network and how much identified devices on that network. You still see the terms in textbooks, exams, and legacy configs, but real networks usually use CIDR and custom subnetting now.

## A quick way to tell classful and classless addressing apart

A simple check helps: look for an explicit prefix length or subnet mask. If you see something like `192.168.1.0/24` or `255.255.255.0`, you are dealing with classless addressing in practice, even if someone casually calls it “Class C.”

If the material only says an address belongs to a class and assumes the default mask from that class, that is classful thinking. That style is common in older books and legacy examples.

You can use this rule of thumb:

- If the mask is spelled out, the network is being treated classlessly.
- If the mask is implied by A, B, or C, the material is using classful rules.
- If the address is in `224.0.0.0/4` or above, you are probably not looking at a normal host address at all.

This is also where people get tripped up on private ranges. Private IP ranges are not the same thing as classes. For example, `10.0.0.0/8`, `172.16.0.0/12`, and `192.168.0.0/16` are private ranges, but they are not “Class A,” “Class B,” and “Class C” in the sense of how modern networks are built. They just happen to sit inside address space that classful networking once grouped a certain way.

Subnet masks are another common source of confusion. A class gives you the old default mask, but the actual mask on a real network may be different. So `192.168.1.0` does not automatically mean `/24` in every case, and `172.16.0.0` does not automatically mean `/16` unless the configuration actually says so.

For day-to-day work, the safest habit is to read the prefix, not the class label. The label may still be present, but the prefix tells you how the network really behaves.

![A laptop sits next to a router on a desk in a simple home network setup.](https://tse1.mm.bing.net/th?q=ethernet%20router%20and%20laptop%20on%20desk%20photo&w=624&h=352&c=7)

## Conclusion

If you see A, B, or C in a guide, translate it into the actual subnet mask or prefix before you use it. That keeps you from mixing up old classful rules with modern CIDR and subnetting. Once you get used to reading \`/24\`, \`/16\`, or \`/8\` directly, the class labels become mostly historical shorthand, which is usually all they are now.

## Frequently Asked Questions

### Is Class C the same as a /24?

In the old classful model, yes: Class C used the default mask \`255.255.255.0\`, which is \`/24\`. In modern networking, though, a \`/24\` is just a prefix length, and people may call it Class C out of habit.

### Are private IP ranges the same as IP classes?

No. Private ranges are specific blocks reserved for internal networks. They overlap with the class system only in the old classful sense, not because they mean the same thing.

### Do routers still use Class A, B, and C?

Modern routing uses CIDR prefixes, not fixed classes. You may still see class labels in old documents or learning material, but actual routing decisions are based on the prefix length and subnet mask.