Data as of Nov 6, 2026
84.238.0.0/17
393 residential-proxy exits · 30 daysBolignet-Aarhus F.M.B.A.
Residential-proxy exits
Proxy exits
393
1.2% of its addresses · 30 days
Always-on exits
48
12% of its exits
Spread
107 of 128
/24s with at least one exit
Providers
99
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
136K observations
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 2Extract
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BirdProxies
- BlurPath
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- KocerRoxy
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PacketStream
- PrivateByte
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- TrueProxies
- TrustProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 84.238.0.0/17 | 32,768 | DK-BNAA-20040730 | Bolignet-Aarhus F.M.B.A. (ORG-BA46-RIPE) · DK | ALLOCATED PA | Jul 30, 2004 | abuse@ |
| └ 84.238.0.0/24 | 256 | BNAA-INTERNAL | unknown | ASSIGNED PA | Aug 2, 2004 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.1.0/25 | 128 | BNAA-INTERCONNECT | BNAA Customer Interconnect | ASSIGNED PA | Feb 8, 2006 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.2.0/24 | 256 | BNAA-INTERNAL | unknown | ASSIGNED PA | Mar 21, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.4.64/29 | 8 | BNAA-CUSTOMER-IP | unknown | ASSIGNED PA | Dec 20, 2004 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.4.96/27 | 32 | BNAA-INTERCONNECT | BNAA Customer Interconnect (/30) | ASSIGNED PA | Jan 21, 2010 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.4.140/30 | 4 | BNAA-DHCP | unknown | ASSIGNED PA | Feb 3, 2006 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.4.160/27 | 32 | BNAA-CUSTOMER-IP | Permanent IP for a customer's machine | ASSIGNED PA | Feb 7, 2006 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.4.192/30 | 4 | BNAA-DHCP | unknown | ASSIGNED PA | Feb 3, 2006 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.4.196/30 | 4 | BNAA-DHCP | unknown | ASSIGNED PA | Feb 3, 2006 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.4.224/27 | 32 | BNAA-CUSTOMER-IP | Permanent IP for a customer's machine | ASSIGNED PA | Feb 7, 2006 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.5.0/27 | 32 | BNAA-CUSTOMER-IP | Customer ID #50054, Router Location:ARH | ASSIGNED PA | Jan 21, 2010 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.5.32/27 | 32 | BNAA-INTERCONNECT | BNAA Customer Interconnect (/30) | ASSIGNED PA | Jan 21, 2010 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.5.64/26 | 64 | BNAA-INTERCONNECT | BNAA Customer Interconnect (/30) | ASSIGNED PA | Jan 21, 2010 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.6.0/25 | 128 | BNAA-INTERCONNECT | Peering and customer interconnect, Location: CPH | ASSIGNED PA | Jan 21, 2010 | abuse@ via DK-BNAA-20040730 |
| └ 84. | 4,352 | BNAA-DHCP | Customer IP | ASSIGNED PA | Nov 25, 2004 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.24.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Mar 21, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.25.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Mar 21, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.26.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Mar 21, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.27.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Mar 21, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.28.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Mar 21, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.29.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.30.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.31.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.32.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.33.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.34.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.35.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.36.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.37.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.38.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.39.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.40.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.41.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.42.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.43.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.44.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.45.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.46.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.47.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.48.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.49.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.50.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.51.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.52.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.53.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.54.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.55.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.56.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.57.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.58.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.62.0/24 | 256 | BNAA-DHCP | unknown | ASSIGNED PA | Apr 25, 2017 | abuse@ via DK-BNAA-20040730 |
| └ 84. | 8,448 | BNAA-DHCP | Dynamic Customer IP's | ASSIGNED PA | Feb 3, 2006 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.100.0/22 | 1,024 | BNAA_ | unknown | ASSIGNED PA | Apr 8, 2010 | abuse@ via DK-BNAA-20040730 |
| └ 84.238.112.0/21 | 2,048 | BNAA-DHCP | unknown | ASSIGNED PA | Sep 5, 2007 | abuse@ via DK-BNAA-20040730 |
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
AS33796
DK
- Name
- Bolignet-Aarhus F.M.B.A.
- Type
- Internet provider
- Registered
- Aug 2, 2004
- Domain
- bolignet-aarhus.dk
- Website
- www.bolignet-aarhus.dk
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Dec 2005
- Current origin since
- Dec 2005 · 21 yr
- Origin networks
- 1
Whois
Registration for this announcement
- Range
- 84.
238. 0. 0/ 17 - Netname
- DK-BNAA-20040730
- Registrant
- Bolignet-Aarhus F.M.B.A.
- Registrant country
- DK
- Organization
- Bolignet-Aarhus F.M.B.A. (ORG-BA46-RIPE)
- Org country
- DK
- Type
- ALLOCATED PA
- Created
- Jul 30, 2004
- Updated
- Oct 9, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- DK
- Delegated
- Jul 30, 2004
- Status
- assigned
Report abuse
Abuse contact
- abuse@
bnaa. dk - Name
- Abuse-C Role
- Handle
- AR14805-RIPE