Data as of Nov 18, 2026

185.52.12.0/22

No anonymizer space · no proxy exits in 30 days

i3D.net B.V

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
185.52.12.0/221,024NL-I3DNET-20140327i3D.net B.V (ORG-IA772-RIPE) · NLALLOCATED PAMar 27, 2014abuse@i3d.net
└ 185.52.12.0/24256Smartdc-Carbon6Smartdc Internet for Offices Carbon6ASSIGNED PAApr 14, 2014abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.13.0/2664Smartdc-nlhen1-sharedcoloSmartdc Heerlen shared colocationASSIGNED PAApr 14, 2014abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.13.64/304i3Dnet-K123949i3D.net Customer K123949ASSIGNED PAMar 24, 2015abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.13.72/298i3Dnet-K132396i3D.net Customer K132396ASSIGNED PAOct 4, 2017abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.13.96/2816i3Dnet-K153316unknownASSIGNED PAMay 10, 2021abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.13.112/298i3Dnet-K546961unknownASSIGNED PADec 22, 2020abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.13.128/2664i3Dnet-K111076i3D.net Customer K111076ASSIGNED PAJun 19, 2015abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.13.192/2732i3Dnet-K124430i3D.net Customer K124430ASSIGNED PAJul 17, 2015abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.13.240/2816i3Dnet-K127448i3D.net Customer K127448ASSIGNED PANov 2, 2015abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.14.0/2816Smartdc-nlhen1-infraunknownASSIGNED PAMay 24, 2016abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.14.32/2732i3Dnet-K124430-2i3D.net Customer K124430ASSIGNED PADec 3, 2015abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.14.72/298i3D-K123445unknownASSIGNED PAJun 14, 2018abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.14.80/2816i3D-K123445unknownASSIGNED PAJul 9, 2018abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.14.160/2816i3D-K123834unknownASSIGNED PAApr 20, 2018abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.14.176/2816i3Dnet-k10011unknownASSIGNED PAMar 28, 2022abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.14.192/2664i3Dnet-nlhen1-sharedcolo-2unknownASSIGNED PAApr 8, 2025abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.15.16/2816i3Dnet-k774417unknownASSIGNED PAJan 8, 2021abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.15.32/298i3Dnet-K153316unknownASSIGNED PAMay 10, 2021abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.15.40/298i3Dnet-K546961unknownASSIGNED PAJun 3, 2021abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.15.48/298i3Dnet-K119739unknownASSIGNED PAJun 11, 2021abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.15.64/2816i3Dnet-K153316unknownASSIGNED PAFeb 4, 2022abuse@i3d.net
via NL-I3DNET-20140327
└ 185.52.15.80/2816i3Dnet-K152812unknownASSIGNED PAApr 20, 2022abuse@i3d.net
via NL-I3DNET-20140327

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Apr 2014
Current origin since
Apr 2014 · 13 yr
Origin networks
1