(Server IPv6 Addresses)

First, we estimate the Entropy for each nybble in the IPv6 addresses, across the whole dataset. For example, if the last nybble is highly variable, then the corresponding Entropy will be high. Conversely, the Entropy will be zero for nybbles that stay constant across the dataset. Below we plot the normalized value of Entropy for each of the 32 nybbles, along with the 4-bit Aggregate Count Ratio, which was introduced in Plonka and Berger, 2015.

Second, we group adjacent nybbles with similar Entropy to form larger **segments**, with
the expectation that they represent semantically different parts of each address.
We label these segments with letters and mark them with dashed lines in the plot below.

Next, we search the segments for the most popular values and ranges of values within them. For that purpose, we use statistical methods for detecting outliers and the DBSCAN machine learning algorithm. We analyze distribution and frequencies of values inside address segments.

Below we present the results, with ranges of values shown as two values in italics (bottom to top). The last column gives the relative frequency across the whole dataset. The /32 prefixes are anonymized.

A: bits 0-32 (hex chars 1- 8)

- 20010db8 53.79%
- 30010db8 22.94%
- 40010db8 12.24%
- 50010db8 3.40%
- 60010db8 2.58%
- 70010db8 2.44%
- 80010db8 1.97%
- 90010db8 0.64%
B: bits 32-36 (hex chars 9- 9)

- f 62.24%
- 0 22.94%
- 7 12.24%
- 3 2.58%
C: bits 36-40 (hex chars 10-10)

- f 62.24%
- 0 37.76%
D: bits 40-44 (hex chars 11-11)

- 0 98.30%
- 1 1.70%
E: bits 44-48 (hex chars 12-12)

- 0 62.24%
- 3 22.94%
- f 14.82%
F: bits 48-64 (hex chars 13-16)

- 0000 100.00%
G: bits 64-96 (hex chars 17-24)

- 00000000 100.00%
H: bits 96-100 (hex chars 25-25)

- 3 73.52%
- 1 8.77%
- 6 5.75%
- b 5.43%
- 2 3.49%
- a 1.50%
- 4 0.90%
- c 0.38%
- 7 0.27%
I: bits 100-108 (hex chars 26-27)

- 6f 14.73%
- 6e 9.88%
- 71 8.77%
- 41 7.30%
- 6d 6.59%
- 40 6.17%
- b1 5.58%
- 21 4.60%
- 6a 4.56%
* 02-f7 31.82%J: bits 108-128 (hex chars 28-32)

- 1efea 0.02%
- 1c73b 0.01%
- 09c61 0.01%
- 50a15 0.01%
- b8362 0.01%
- 5ccaa 0.01%
- 371be 0.01%
- 264bd 0.01%
- 36c3d 0.01%
- 2edc2 0.01%
* 052ee-7ffd7 68.27%* b1013-ffee5 16.70%* 000ea-b0e03 14.89%

Next, we search for statistical dependencies between the segments. For that purpose, we train a Bayesian Network (BN) from data.

Below we show structure of the corresponding BN model. Arrows indicate direct statistical influence. Note that directly connected segments can probabilistically influence each other in both directions (upstream / downstream). Under some conditions, segments without direct connection can still influence each other through other segments: e.g., A can influence C through B if C depends on B and B depends on A (even if there is no direct arrow between A and C).

Learning BN structure from data is in general a challenging optimization problem. Hence, there might be more than one possible BN structure graph for the same dataset.

Finally, below we show an interactive browser that decomposes IPv6 addresses into segments, values, ranges, and their corresponding probabilities. The browser lets for exploring the underlying BN model and see how certain segment values probabilistically influence the other segments.

Try clicking on the colored boxes below. You should see the colors changing, which reflects
the fact that some segment values can make the other values more (or less) likely. For instance,
in the Sample Report, you may find that clicking on
**J1** (i.e., the first value in segment **J**) makes segments **C, D, F, H,** and
**I** largely predictable (see our paper for more examples).

You may condition the model on many segment values. Clicking on selected values un-selects them. Clicking on the red "Clear" above the color map un-selects them all. Below the browser we show the estimated proportion of the addresses matching your selection (vs. the dataset). If the browser cannot estimate the probabilities in a reasonable time, it asks before trying harder.

Loading...

Using the BN model, below we generate a few candidate target IPv6 addresses matching the selection above. Note that we anonymize the IPv6 addresses in this report.

As we show in the paper, this technique allowed us to successfully scan IPv6 networks of servers and routers, and to predict the IPv6 network identifiers of active client IPv6 addresses.