What are the valid public ip address ranges
up vote
2
down vote
favorite
1
There are a number of lists on the web that define all valid public ip addresses ranges but they don't seem to be very accurate.
The most common list Ive found is show below. This list however doesn't include addresses in 191.236.x.x even though there are public web servers in that range.
Is there a definitive and correct list?
- 1.0.0.0 - 9.255.255.255
- 11.0.0.0 - 126.255.255.255
- 129.0.0.0 - 169.253.255.255
- 169.255.0.0 - 172.15.255.255
- 172.32.0.0 - 191.0.1.255
- 192.0.3.0 - 192.88.98.255
- 192.88.100.0 - 192.167.255.255
- 192.169.0.0 - 198.17.255.255
- 198.20.0.0 - 223.255.255.255
ip-address range list
asked Mar 16 '16 at 23:38
PeterJ
59114
add a comment |
up vote
2
down vote
favorite
1
There are a number of lists on the web that define all valid public ip addresses ranges but they don't seem to be very accurate.
The most common list Ive found is show below. This list however doesn't include addresses in 191.236.x.x even though there are public web servers in that range.
Is there a definitive and correct list?
- 1.0.0.0 - 9.255.255.255
- 11.0.0.0 - 126.255.255.255
- 129.0.0.0 - 169.253.255.255
- 169.255.0.0 - 172.15.255.255
- 172.32.0.0 - 191.0.1.255
- 192.0.3.0 - 192.88.98.255
- 192.88.100.0 - 192.167.255.255
- 192.169.0.0 - 198.17.255.255
- 198.20.0.0 - 223.255.255.255
ip-address range list
asked Mar 16 '16 at 23:38
PeterJ
59114
What has your research shown. The list you have isn't complete.
– Ramhound
Mar 17 '16 at 2:08
1
Thats the point of the question
– PeterJ
Mar 24 '16 at 21:45
add a comment |
up vote
2
down vote
favorite
1
up vote
2
down vote
favorite
1
1
There are a number of lists on the web that define all valid public ip addresses ranges but they don't seem to be very accurate.
The most common list Ive found is show below. This list however doesn't include addresses in 191.236.x.x even though there are public web servers in that range.
Is there a definitive and correct list?
- 1.0.0.0 - 9.255.255.255
- 11.0.0.0 - 126.255.255.255
- 129.0.0.0 - 169.253.255.255
- 169.255.0.0 - 172.15.255.255
- 172.32.0.0 - 191.0.1.255
- 192.0.3.0 - 192.88.98.255
- 192.88.100.0 - 192.167.255.255
- 192.169.0.0 - 198.17.255.255
- 198.20.0.0 - 223.255.255.255
ip-address range list
asked Mar 16 '16 at 23:38
PeterJ
59114
There are a number of lists on the web that define all valid public ip addresses ranges but they don't seem to be very accurate.
The most common list Ive found is show below. This list however doesn't include addresses in 191.236.x.x even though there are public web servers in that range.
Is there a definitive and correct list?
- 1.0.0.0 - 9.255.255.255
- 11.0.0.0 - 126.255.255.255
- 129.0.0.0 - 169.253.255.255
- 169.255.0.0 - 172.15.255.255
- 172.32.0.0 - 191.0.1.255
- 192.0.3.0 - 192.88.98.255
- 192.88.100.0 - 192.167.255.255
- 192.169.0.0 - 198.17.255.255
- 198.20.0.0 - 223.255.255.255
ip-address range list
ip-address range list
asked Mar 16 '16 at 23:38
PeterJ
59114
asked Mar 16 '16 at 23:38
PeterJ
59114
asked Mar 16 '16 at 23:38
PeterJ
59114
asked Mar 16 '16 at 23:38
PeterJ
59114
asked Mar 16 '16 at 23:38
PeterJ
59114
59114
What has your research shown. The list you have isn't complete.
– Ramhound
Mar 17 '16 at 2:08
1
Thats the point of the question
– PeterJ
Mar 24 '16 at 21:45
add a comment |
What has your research shown. The list you have isn't complete.
– Ramhound
Mar 17 '16 at 2:08
1
Thats the point of the question
– PeterJ
Mar 24 '16 at 21:45
What has your research shown. The list you have isn't complete.
– Ramhound
Mar 17 '16 at 2:08
What has your research shown. The list you have isn't complete.
– Ramhound
Mar 17 '16 at 2:08
1
1
Thats the point of the question
– PeterJ
Mar 24 '16 at 21:45
Thats the point of the question
– PeterJ
Mar 24 '16 at 21:45
add a comment |
3 Answers
3
active
oldest
votes
up vote
8
down vote
IANA provides standards on this subject. For IPv4, here is what they have in their "special purpose address registry". Meaning, for our purposes, anything in these address blocks shouldn't be assigned because they shouldn't be routable "publicly".
0.0.0.0/8
10.0.0.0/8
100.64.0.0/10
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.0.0.0/24
192.0.0.0/29
192.0.0.8/32
192.0.0.9/32
192.0.0.170/32
192.0.0.171/32
192.0.2.0/24
192.31.196.0/24
192.52.193.0/24
192.88.99.0/24
192.168.0.0/16
192.175.48.0/24
198.18.0.0/15
198.51.100.0/24
203.0.113.0/24
240.0.0.0/4
255.255.255.255/32
(Edit, also)
224.0.0.0/24
239.0.0.0/8
This is more consistent with the example you provided above.
If you don't understand CIDR notation, you can convert them to ranges here.
answered Mar 17 '16 at 0:19
BrianC
67139
You forgot the multicast addresses, which, from a practical perspective, cannot be used on the Internet.224.0.0.0/4.
– Ron Maupin
Mar 17 '16 at 0:27
@RonMaupin That's true, thanks. I added that (as well as 239.0.0.0/8) to my post.
– BrianC
Mar 17 '16 at 0:42
Also, there are IPv4 bogon lists which many ISPs use to block addresses from being routed on the Internet, e.g. team-cymru.org/Services/Bogons/fullbogons-ipv4.txt "A bogon prefix is a route that should never appear in the Internet routing table. A packet routed over the public Internet (not including over VPNs or other tunnels) should never have a source address in a bogon range."
– Ron Maupin
Mar 17 '16 at 0:46
Well...I guess it really boils down to whether or not you consider valid "public" ranges to be not assigned, or not reserved.
– BrianC
Mar 17 '16 at 0:50
1
Thanks for the response but the point of question was to provide a reference for the valid ranges not the exclusions
– PeterJ
Mar 24 '16 at 21:49
|
show 3 more comments
up vote
0
down vote
- 1.0.0.0-9.255.255.255
- 11.0.0.0-100.63.255.255
- 100.128.0.0-126.255.255.255
- 128.0.0.0-169.253.255.255
- 169.255.0.0-172.15.255.255
- 172.32.0.0-191.255.255.255
- 192.0.1.0/24
- 192.0.3.0-192.88.98.255
- 192.88.100.0-192.167.255.255
- 192.169.0.0-198.17.255.255
- 198.20.0.0-198.51.99.255
- 198.51.101.0-203.0.112.255
- 203.0.114.0-223.255.255.255
edited Nov 23 at 11:28
Scott
15.5k113789
answered Nov 23 at 11:22
hmuller
1
add a comment |
up vote
-1
down vote
All IP address from 1 to 191 excluding the RFC1918 private addresses below are assigned for Public IPs.:
RFC1918 - Private address alocation:
- 10.0.0.0 - 10.255.255.255 (10/8 prefix)
- 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
- 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
edited Nov 23 at 13:01
tripleee
1,72832130
answered Sep 19 at 14:26
Muhammad Riaz
1
1
Not all of them. (100.64.0.0/10 for example?) And the public allocations don't end at 191, they continue all the way to 223.
– grawity
Sep 19 at 14:29
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
8
down vote
IANA provides standards on this subject. For IPv4, here is what they have in their "special purpose address registry". Meaning, for our purposes, anything in these address blocks shouldn't be assigned because they shouldn't be routable "publicly".
0.0.0.0/8
10.0.0.0/8
100.64.0.0/10
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.0.0.0/24
192.0.0.0/29
192.0.0.8/32
192.0.0.9/32
192.0.0.170/32
192.0.0.171/32
192.0.2.0/24
192.31.196.0/24
192.52.193.0/24
192.88.99.0/24
192.168.0.0/16
192.175.48.0/24
198.18.0.0/15
198.51.100.0/24
203.0.113.0/24
240.0.0.0/4
255.255.255.255/32
(Edit, also)
224.0.0.0/24
239.0.0.0/8
This is more consistent with the example you provided above.
If you don't understand CIDR notation, you can convert them to ranges here.
answered Mar 17 '16 at 0:19
BrianC
67139
You forgot the multicast addresses, which, from a practical perspective, cannot be used on the Internet.224.0.0.0/4.
– Ron Maupin
Mar 17 '16 at 0:27
@RonMaupin That's true, thanks. I added that (as well as 239.0.0.0/8) to my post.
– BrianC
Mar 17 '16 at 0:42
Also, there are IPv4 bogon lists which many ISPs use to block addresses from being routed on the Internet, e.g. team-cymru.org/Services/Bogons/fullbogons-ipv4.txt "A bogon prefix is a route that should never appear in the Internet routing table. A packet routed over the public Internet (not including over VPNs or other tunnels) should never have a source address in a bogon range."
– Ron Maupin
Mar 17 '16 at 0:46
Well...I guess it really boils down to whether or not you consider valid "public" ranges to be not assigned, or not reserved.
– BrianC
Mar 17 '16 at 0:50
1
Thanks for the response but the point of question was to provide a reference for the valid ranges not the exclusions
– PeterJ
Mar 24 '16 at 21:49
|
show 3 more comments
up vote
8
down vote
IANA provides standards on this subject. For IPv4, here is what they have in their "special purpose address registry". Meaning, for our purposes, anything in these address blocks shouldn't be assigned because they shouldn't be routable "publicly".
0.0.0.0/8
10.0.0.0/8
100.64.0.0/10
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.0.0.0/24
192.0.0.0/29
192.0.0.8/32
192.0.0.9/32
192.0.0.170/32
192.0.0.171/32
192.0.2.0/24
192.31.196.0/24
192.52.193.0/24
192.88.99.0/24
192.168.0.0/16
192.175.48.0/24
198.18.0.0/15
198.51.100.0/24
203.0.113.0/24
240.0.0.0/4
255.255.255.255/32
(Edit, also)
224.0.0.0/24
239.0.0.0/8
This is more consistent with the example you provided above.
If you don't understand CIDR notation, you can convert them to ranges here.
answered Mar 17 '16 at 0:19
BrianC
67139
You forgot the multicast addresses, which, from a practical perspective, cannot be used on the Internet.224.0.0.0/4.
– Ron Maupin
Mar 17 '16 at 0:27
@RonMaupin That's true, thanks. I added that (as well as 239.0.0.0/8) to my post.
– BrianC
Mar 17 '16 at 0:42
Also, there are IPv4 bogon lists which many ISPs use to block addresses from being routed on the Internet, e.g. team-cymru.org/Services/Bogons/fullbogons-ipv4.txt "A bogon prefix is a route that should never appear in the Internet routing table. A packet routed over the public Internet (not including over VPNs or other tunnels) should never have a source address in a bogon range."
– Ron Maupin
Mar 17 '16 at 0:46
Well...I guess it really boils down to whether or not you consider valid "public" ranges to be not assigned, or not reserved.
– BrianC
Mar 17 '16 at 0:50
1
Thanks for the response but the point of question was to provide a reference for the valid ranges not the exclusions
– PeterJ
Mar 24 '16 at 21:49
|
show 3 more comments
up vote
8
down vote
up vote
8
down vote
IANA provides standards on this subject. For IPv4, here is what they have in their "special purpose address registry". Meaning, for our purposes, anything in these address blocks shouldn't be assigned because they shouldn't be routable "publicly".
0.0.0.0/8
10.0.0.0/8
100.64.0.0/10
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.0.0.0/24
192.0.0.0/29
192.0.0.8/32
192.0.0.9/32
192.0.0.170/32
192.0.0.171/32
192.0.2.0/24
192.31.196.0/24
192.52.193.0/24
192.88.99.0/24
192.168.0.0/16
192.175.48.0/24
198.18.0.0/15
198.51.100.0/24
203.0.113.0/24
240.0.0.0/4
255.255.255.255/32
(Edit, also)
224.0.0.0/24
239.0.0.0/8
This is more consistent with the example you provided above.
If you don't understand CIDR notation, you can convert them to ranges here.
answered Mar 17 '16 at 0:19
BrianC
67139
IANA provides standards on this subject. For IPv4, here is what they have in their "special purpose address registry". Meaning, for our purposes, anything in these address blocks shouldn't be assigned because they shouldn't be routable "publicly".
0.0.0.0/8
10.0.0.0/8
100.64.0.0/10
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.0.0.0/24
192.0.0.0/29
192.0.0.8/32
192.0.0.9/32
192.0.0.170/32
192.0.0.171/32
192.0.2.0/24
192.31.196.0/24
192.52.193.0/24
192.88.99.0/24
192.168.0.0/16
192.175.48.0/24
198.18.0.0/15
198.51.100.0/24
203.0.113.0/24
240.0.0.0/4
255.255.255.255/32
(Edit, also)
224.0.0.0/24
239.0.0.0/8
This is more consistent with the example you provided above.
If you don't understand CIDR notation, you can convert them to ranges here.
answered Mar 17 '16 at 0:19
BrianC
67139
edited Mar 17 '16 at 0:41
answered Mar 17 '16 at 0:19
BrianC
67139
answered Mar 17 '16 at 0:19
BrianC
67139
answered Mar 17 '16 at 0:19
BrianC
67139
67139
You forgot the multicast addresses, which, from a practical perspective, cannot be used on the Internet.224.0.0.0/4.
– Ron Maupin
Mar 17 '16 at 0:27
@RonMaupin That's true, thanks. I added that (as well as 239.0.0.0/8) to my post.
– BrianC
Mar 17 '16 at 0:42
Also, there are IPv4 bogon lists which many ISPs use to block addresses from being routed on the Internet, e.g. team-cymru.org/Services/Bogons/fullbogons-ipv4.txt "A bogon prefix is a route that should never appear in the Internet routing table. A packet routed over the public Internet (not including over VPNs or other tunnels) should never have a source address in a bogon range."
– Ron Maupin
Mar 17 '16 at 0:46
Well...I guess it really boils down to whether or not you consider valid "public" ranges to be not assigned, or not reserved.
– BrianC
Mar 17 '16 at 0:50
1
Thanks for the response but the point of question was to provide a reference for the valid ranges not the exclusions
– PeterJ
Mar 24 '16 at 21:49
|
show 3 more comments
You forgot the multicast addresses, which, from a practical perspective, cannot be used on the Internet.224.0.0.0/4.
– Ron Maupin
Mar 17 '16 at 0:27
@RonMaupin That's true, thanks. I added that (as well as 239.0.0.0/8) to my post.
– BrianC
Mar 17 '16 at 0:42
Also, there are IPv4 bogon lists which many ISPs use to block addresses from being routed on the Internet, e.g. team-cymru.org/Services/Bogons/fullbogons-ipv4.txt "A bogon prefix is a route that should never appear in the Internet routing table. A packet routed over the public Internet (not including over VPNs or other tunnels) should never have a source address in a bogon range."
– Ron Maupin
Mar 17 '16 at 0:46
Well...I guess it really boils down to whether or not you consider valid "public" ranges to be not assigned, or not reserved.
– BrianC
Mar 17 '16 at 0:50
1
Thanks for the response but the point of question was to provide a reference for the valid ranges not the exclusions
– PeterJ
Mar 24 '16 at 21:49
You forgot the multicast addresses, which, from a practical perspective, cannot be used on the Internet.
224.0.0.0/4.– Ron Maupin
Mar 17 '16 at 0:27
You forgot the multicast addresses, which, from a practical perspective, cannot be used on the Internet.
224.0.0.0/4.– Ron Maupin
Mar 17 '16 at 0:27
@RonMaupin That's true, thanks. I added that (as well as 239.0.0.0/8) to my post.
– BrianC
Mar 17 '16 at 0:42
@RonMaupin That's true, thanks. I added that (as well as 239.0.0.0/8) to my post.
– BrianC
Mar 17 '16 at 0:42
Also, there are IPv4 bogon lists which many ISPs use to block addresses from being routed on the Internet, e.g. team-cymru.org/Services/Bogons/fullbogons-ipv4.txt "A bogon prefix is a route that should never appear in the Internet routing table. A packet routed over the public Internet (not including over VPNs or other tunnels) should never have a source address in a bogon range."
– Ron Maupin
Mar 17 '16 at 0:46
Also, there are IPv4 bogon lists which many ISPs use to block addresses from being routed on the Internet, e.g. team-cymru.org/Services/Bogons/fullbogons-ipv4.txt "A bogon prefix is a route that should never appear in the Internet routing table. A packet routed over the public Internet (not including over VPNs or other tunnels) should never have a source address in a bogon range."
– Ron Maupin
Mar 17 '16 at 0:46
Well...I guess it really boils down to whether or not you consider valid "public" ranges to be not assigned, or not reserved.
– BrianC
Mar 17 '16 at 0:50
Well...I guess it really boils down to whether or not you consider valid "public" ranges to be not assigned, or not reserved.
– BrianC
Mar 17 '16 at 0:50
1
1
Thanks for the response but the point of question was to provide a reference for the valid ranges not the exclusions
– PeterJ
Mar 24 '16 at 21:49
Thanks for the response but the point of question was to provide a reference for the valid ranges not the exclusions
– PeterJ
Mar 24 '16 at 21:49
|
show 3 more comments
up vote
0
down vote
- 1.0.0.0-9.255.255.255
- 11.0.0.0-100.63.255.255
- 100.128.0.0-126.255.255.255
- 128.0.0.0-169.253.255.255
- 169.255.0.0-172.15.255.255
- 172.32.0.0-191.255.255.255
- 192.0.1.0/24
- 192.0.3.0-192.88.98.255
- 192.88.100.0-192.167.255.255
- 192.169.0.0-198.17.255.255
- 198.20.0.0-198.51.99.255
- 198.51.101.0-203.0.112.255
- 203.0.114.0-223.255.255.255
edited Nov 23 at 11:28
Scott
15.5k113789
answered Nov 23 at 11:22
hmuller
1
add a comment |
up vote
0
down vote
- 1.0.0.0-9.255.255.255
- 11.0.0.0-100.63.255.255
- 100.128.0.0-126.255.255.255
- 128.0.0.0-169.253.255.255
- 169.255.0.0-172.15.255.255
- 172.32.0.0-191.255.255.255
- 192.0.1.0/24
- 192.0.3.0-192.88.98.255
- 192.88.100.0-192.167.255.255
- 192.169.0.0-198.17.255.255
- 198.20.0.0-198.51.99.255
- 198.51.101.0-203.0.112.255
- 203.0.114.0-223.255.255.255
edited Nov 23 at 11:28
Scott
15.5k113789
answered Nov 23 at 11:22
hmuller
1
add a comment |
up vote
0
down vote
up vote
0
down vote
- 1.0.0.0-9.255.255.255
- 11.0.0.0-100.63.255.255
- 100.128.0.0-126.255.255.255
- 128.0.0.0-169.253.255.255
- 169.255.0.0-172.15.255.255
- 172.32.0.0-191.255.255.255
- 192.0.1.0/24
- 192.0.3.0-192.88.98.255
- 192.88.100.0-192.167.255.255
- 192.169.0.0-198.17.255.255
- 198.20.0.0-198.51.99.255
- 198.51.101.0-203.0.112.255
- 203.0.114.0-223.255.255.255
edited Nov 23 at 11:28
Scott
15.5k113789
answered Nov 23 at 11:22
hmuller
1
- 1.0.0.0-9.255.255.255
- 11.0.0.0-100.63.255.255
- 100.128.0.0-126.255.255.255
- 128.0.0.0-169.253.255.255
- 169.255.0.0-172.15.255.255
- 172.32.0.0-191.255.255.255
- 192.0.1.0/24
- 192.0.3.0-192.88.98.255
- 192.88.100.0-192.167.255.255
- 192.169.0.0-198.17.255.255
- 198.20.0.0-198.51.99.255
- 198.51.101.0-203.0.112.255
- 203.0.114.0-223.255.255.255
edited Nov 23 at 11:28
Scott
15.5k113789
answered Nov 23 at 11:22
hmuller
1
edited Nov 23 at 11:28
Scott
15.5k113789
edited Nov 23 at 11:28
Scott
15.5k113789
edited Nov 23 at 11:28
Scott
15.5k113789
15.5k113789
answered Nov 23 at 11:22
hmuller
1
answered Nov 23 at 11:22
hmuller
1
answered Nov 23 at 11:22
hmuller
1
1
add a comment |
add a comment |
up vote
-1
down vote
All IP address from 1 to 191 excluding the RFC1918 private addresses below are assigned for Public IPs.:
RFC1918 - Private address alocation:
- 10.0.0.0 - 10.255.255.255 (10/8 prefix)
- 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
- 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
edited Nov 23 at 13:01
tripleee
1,72832130
answered Sep 19 at 14:26
Muhammad Riaz
1
1
Not all of them. (100.64.0.0/10 for example?) And the public allocations don't end at 191, they continue all the way to 223.
– grawity
Sep 19 at 14:29
add a comment |
up vote
-1
down vote
All IP address from 1 to 191 excluding the RFC1918 private addresses below are assigned for Public IPs.:
RFC1918 - Private address alocation:
- 10.0.0.0 - 10.255.255.255 (10/8 prefix)
- 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
- 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
edited Nov 23 at 13:01
tripleee
1,72832130
answered Sep 19 at 14:26
Muhammad Riaz
1
1
Not all of them. (100.64.0.0/10 for example?) And the public allocations don't end at 191, they continue all the way to 223.
– grawity
Sep 19 at 14:29
add a comment |
up vote
-1
down vote
up vote
-1
down vote
All IP address from 1 to 191 excluding the RFC1918 private addresses below are assigned for Public IPs.:
RFC1918 - Private address alocation:
- 10.0.0.0 - 10.255.255.255 (10/8 prefix)
- 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
- 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
edited Nov 23 at 13:01
tripleee
1,72832130
answered Sep 19 at 14:26
Muhammad Riaz
1
All IP address from 1 to 191 excluding the RFC1918 private addresses below are assigned for Public IPs.:
RFC1918 - Private address alocation:
- 10.0.0.0 - 10.255.255.255 (10/8 prefix)
- 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
- 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
edited Nov 23 at 13:01
tripleee
1,72832130
answered Sep 19 at 14:26
Muhammad Riaz
1
edited Nov 23 at 13:01
tripleee
1,72832130
edited Nov 23 at 13:01
tripleee
1,72832130
edited Nov 23 at 13:01
tripleee
1,72832130
1,72832130
answered Sep 19 at 14:26
Muhammad Riaz
1
answered Sep 19 at 14:26
Muhammad Riaz
1
answered Sep 19 at 14:26
Muhammad Riaz
1
1
1
Not all of them. (100.64.0.0/10 for example?) And the public allocations don't end at 191, they continue all the way to 223.
– grawity
Sep 19 at 14:29
add a comment |
1
Not all of them. (100.64.0.0/10 for example?) And the public allocations don't end at 191, they continue all the way to 223.
– grawity
Sep 19 at 14:29
1
1
Not all of them. (100.64.0.0/10 for example?) And the public allocations don't end at 191, they continue all the way to 223.
– grawity
Sep 19 at 14:29
Not all of them. (100.64.0.0/10 for example?) And the public allocations don't end at 191, they continue all the way to 223.
– grawity
Sep 19 at 14:29
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1053845%2fwhat-are-the-valid-public-ip-address-ranges%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What has your research shown. The list you have isn't complete.
– Ramhound
Mar 17 '16 at 2:08
1
Thats the point of the question
– PeterJ
Mar 24 '16 at 21:45