Data as of Nov 14, 2026

89.207.128.0/24

No anonymizer space · no proxy exits in 30 days

Snel.com 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
89.207.128.0/24256NL-SNEL-COM-20081205Snel.com B.V. (ORG-PIS14-RIPE) · NLALLOCATED PAFeb 13, 2026report@abuse.bz
└ 89.207.128.200/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.201/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.202/321NL-SNEL-SERVER-190IP Range Snel.com assigned to server #190ASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.203/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.204/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.205/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.206/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.207/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.208/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.209/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.210/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.211/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.212/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.213/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.214/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.215/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.216/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.217/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.218/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.219/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.220/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.221/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.222/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.223/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.224/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.225/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.226/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.227/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.228/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.229/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.230/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.231/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.232/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.233/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.234/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.235/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.236/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.237/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.238/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.239/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.240/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.241/321TorServersTor ServersASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.242/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.243/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.244/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.245/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.246/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.247/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.248/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.249/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.250/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.251/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.252/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.253/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.254/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
└ 89.207.128.255/321NL-SNELIP Range Snel.comASSIGNED PAFeb 17, 2012report@abuse.bz
via NL-SNEL-COM-20081205
← Previous201–256 of 256 · page 2 of 2Next →

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

Origin network

AS62370

NL
Name
Snel.com B.V.
Type
Hosting
Registered
Oct 18, 2013
Domain
snel.com
Industry
Hosting and Cloud Provider
Spamhaus ASN-DROP
not listed