| 2a00::/11 | WHOIS (RIPE_NCC) | RIPE Network Coordination Center | EU |
| 2a10:eec0::/32 | WHOIS (RIPE_NCC) | VeriSign Inc. | CH |
| 2a10:eec0::/32 | RIPE_NCC assigned | — | US |
| 2a10:eec0::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0::/48 | WHOIS (RIPE_NCC) | sesto-1 | SE |
| 2a10:eec0:1::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:1::/48 | WHOIS (RIPE_NCC) | sesto-2 | SE |
| 2a10:eec0:2::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:2::/48 | WHOIS (RIPE_NCC) | nlams-1a | NL |
| 2a10:eec0:3::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:3::/48 | WHOIS (RIPE_NCC) | nlams-1b | NL |
| 2a10:eec0:4::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:4::/48 | WHOIS (RIPE_NCC) | nlams-1c | NL |
| 2a10:eec0:5::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:5::/48 | WHOIS (RIPE_NCC) | nlams-1d | NL |
| 2a10:eec0:6::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:6::/48 | WHOIS (RIPE_NCC) | nlams-1e | NL |
| 2a10:eec0:7::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:7::/48 | WHOIS (RIPE_NCC) | frmrs-1 | FR |
| 2a10:eec0:8::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:8::/48 | WHOIS (RIPE_NCC) | frmrs-2 | FR |
| 2a10:eec0:9::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:9::/48 | WHOIS (RIPE_NCC) | frmrs-3 | FR |
| 2a10:eec0:10::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:10::/48 | WHOIS (RIPE_NCC) | defra-1d | DE |
| 2a10:eec0:11::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:11::/48 | WHOIS (RIPE_NCC) | defra-1e | DE |
| 2a10:eec0:12::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:12::/48 | WHOIS (RIPE_NCC) | defra-2a | DE |
| 2a10:eec0:13::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:13::/48 | WHOIS (RIPE_NCC) | defra-2b | DE |
| 2a10:eec0:14::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:14::/48 | WHOIS (RIPE_NCC) | defra-2c | DE |
| 2a10:eec0:15::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:15::/48 | WHOIS (RIPE_NCC) | defra-7a | DE |
| 2a10:eec0:16::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:16::/48 | WHOIS (RIPE_NCC) | defra-7b | DE |
| 2a10:eec0:17::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:17::/48 | WHOIS (RIPE_NCC) | defra-2 | DE |
| 2a10:eec0:18::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:18::/48 | WHOIS (RIPE_NCC) | defra-7 | DE |
| 2a10:eec0:a::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:a::/48 | WHOIS (RIPE_NCC) | frpar-1 | FR |
| 2a10:eec0:b::/48 | BGP route | AS396828 VeriSign Global Registry Services | — |
| 2a10:eec0:b::/48 | WHOIS (RIPE_NCC) | iad1 | US |
| 2a10:eec0:c::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:c::/48 | WHOIS (RIPE_NCC) | sesto-3 | SE |
| 2a10:eec0:d::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:d::/48 | WHOIS (RIPE_NCC) | defra-1a | DE |
| 2a10:eec0:e::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:e::/48 | WHOIS (RIPE_NCC) | defra-1b | DE |
| 2a10:eec0:f::/48 | BGP route | AS7342 VeriSign Infrastructure & Operations | — |
| 2a10:eec0:f::/48 | WHOIS (RIPE_NCC) | defra-1c | DE |