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

95.80.128.0/21

4 residential-proxy exits · 30 days

Bozorg Net-e Aria

Announcement
95.80.128.0/20
RPKI valid
Announced by
AS48431
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
0.20% of its addresses · 30 days
Spread
3 of 8
/24s with at least one exit
Providers
13
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

59 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.80.128.0/2402
95.80.132.0/2401
95.80.135.0/2401

Proxy providers listing exits

  • BirdProxies
  • Byteful
  • DataImpulse
  • GSocks
  • Geonix
  • Infatica
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Q2IP
  • Shifter

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.80.128.0/18
since Dec 2008
AS48431Residential303
23 always on
Bozorg Net-e Aria

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.80.128.0/1816,384IR-BOZORGNET-20081125Bozorg Net-e Aria (ORG-BNA6-RIPE) · IRALLOCATED PANov 25, 2008abuse@maxnet.ir
└ 95.80.128.0/221,024MXNT-TBZ-DSL-PHASE-1Maxnet DSL Network (Tabriz)ASSIGNED PASep 23, 2011abuse@maxnet.ir
via IR-BOZORGNET-20081125
└ 95.80.132.0/221,024MXNT-TBZ-DSL-PHASE-2Maxnet DSL Network (Tabriz)ASSIGNED PASep 23, 2011abuse@maxnet.ir
via IR-BOZORGNET-20081125

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

Covering aggregate above, the prefix's own history below

95.80.128.0/20

Routing history

Pattern
Stable
First seen
Oct 2018
Current origin since
Oct 2018 · 8.0 yr
Origin networks
1