LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

46.166.176.0/21

No anonymizer space · no proxy exits in 30 days

NForce Entertainment B.V.

Announcement
this exact prefix
RPKI valid
Announced by
AS43350
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
46.166.176.0/204,096NL-NFORCE-20101216NForce Entertainment B.V. (ORG-NE3-RIPE) · NLALLOCATED PAOct 2, 2013abuse@nforce.com
└ 46.166.176.112/2816NFORCE_ENTERTAINMENTCustomer 2033ASSIGNED PADec 31, 2017abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.176.128/25128NFORCE_ENTERTAINMENTCustomer 797ASSIGNED PAJan 22, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.177.0/2732SECUREST_LTDSecurest LTD (ORG-SL141-RIPE)ASSIGNED PADec 24, 2017abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.177.32/2732NFORCE_ENTERTAINMENTCustomer 1835ASSIGNED PAMay 28, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.177.64/2816NFORCE_ENTERTAINMENTCustomer 1946ASSIGNED PAJun 8, 2018abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.177.80/2816NFORCE_ENTERTAINMENTCustomer 1222 / 771ASSIGNED PAMar 11, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.177.96/2816NFORCE_ENTERTAINMENTCustomer 1286ASSIGNED PAApr 8, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.177.112/298NFORCE_ENTERTAINMENTCustomer 4789ASSIGNED PAMay 31, 2022abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.177.120/298NFORCE_ENTERTAINMENTCustomer 1746ASSIGNED PADec 1, 2015abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.177.128/25128CDNVIDEO_RUCustomer 831 / CDNvideo.ruASSIGNED PAJan 30, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.178.0/2816NFORCE_ENTERTAINMENTCustomer 1839ASSIGNED PASep 18, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.178.32/2816NFORCE_ENTERTAINMENTCustomer 906ASSIGNED PAMay 7, 2020abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.178.48/2816NFORCE_ENTERTAINMENTCustomer 824ASSIGNED PAAug 14, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.178.64/2816OWNCUBENForce Entertainment B.V. (ORG-NE3-RIPE) · NLASSIGNED PADec 12, 2015abuse@nforce.com
└ 46.166.178.80/298NFORCE_ENTERTAINMENTCustomer 3830ASSIGNED PAJul 1, 2020abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.178.96/2732NFORCE_ENTERTAINMENTCustomer 1404 - Coin ProjectASSIGNED PANov 27, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.178.192/2732NFORCE_ENTERTAINMENTCustomer 2555ASSIGNED PAJul 21, 2017abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.64/2816NFORCE_ENTERTAINMENTCustomer 3004ASSIGNED PAApr 12, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.80/2816SECUREST_LTDSecurest LTD (ORG-SL141-RIPE)ASSIGNED PAMar 22, 2017abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.96/2816NFORCE_ENTERTAINMENTCustomer 1309ASSIGNED PAMay 11, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.112/2816NFORCE_ENTERTAINMENTCustomer 319ASSIGNED PAJun 6, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.128/2816NFORCE_ENTERTAINMENTCustomer 3743ASSIGNED PAJun 16, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.160/2816NFORCE_ENTERTAINMENTCustomer 2087ASSIGNED PANov 28, 2016abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.176/2816NFORCE_ENTERTAINMENTCustomer 1884ASSIGNED PASep 23, 2016abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.192/2816NFORCE_ENTERTAINMENTCustomer 906ASSIGNED PAJun 6, 2020abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.208/2816NFORCE_ENTERTAINMENTCustomer 3100ASSIGNED PANov 6, 2017abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.224/2816NFORCE_ENTERTAINMENTCustomer 906ASSIGNED PAAug 11, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.179.240/2816NFORCE_ENTERTAINMENTunknownASSIGNED PAAug 11, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.182.0/24256NFORCE_ENTERTAINMENTNForce Entertainment B.V. (ORG-NE3-RIPE) · NLASSIGNED PASep 5, 2014abuse@nforce.com

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
Sep 2014 · 12 yr
Origin networks
2
Last change of origin
Sep 2014
Recorded history

History

Handoffs
1