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

80.71.96.0/20

1 residential-proxy exit · 30 days

GO p.l.c.

Announcement
this exact prefix
RPKI valid
Announced by
AS15735
Type
Residential
89% of it

Residential-proxy exits

Proxy exits
1
0.02% of its addresses · 30 days
Spread
1 of 16
/24s with at least one exit
Providers
14
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

13 observations

Proxy providers listing exits

  • BottingTools
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FastProxy
  • GeekProxy
  • LemonBright
  • LudaxProxy
  • Oxylabs
  • PSBProxy
  • Proxy4U
  • TrustProxy
  • VProxy

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
80.71.96.0/204,096MT-GO-20010607GO p.l.c. (ORG-DL6-RIPE) · MTALLOCATED PASep 19, 2002abuse@go.com.mt
└ 80.71.96.0/221,024KeyworldKeyworld - Internet Service ProviderASSIGNED PAJun 26, 2002abuse@go.com.mt
via MT-GO-20010607
└ 80.71.100.0/23512MT-GO-PLUS-RETAIL-FIXEDDSL-20110103Go Fixed IP UsersASSIGNED PAOct 18, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.102.0/24256keyworld_bras_vrfkeyworld bras vrfASSIGNED PAMay 7, 2010abuse@go.com.mt
via MT-GO-20010607
└ 80.71.104.128/2732PLAYMOBILPlaymobile IP RangeASSIGNED PAJan 6, 2005abuse@go.com.mt
via MT-GO-20010607
└ 80.71.104.240/2816PTLPhilip Toledo LimitedASSIGNED PANov 12, 2007abuse@go.com.mt
via MT-GO-20010607
└ 80.71.105.0/24256keyworld_servers_range_2keyworld servers range 2ASSIGNED PAMay 7, 2010abuse@go.com.mt
via MT-GO-20010607
└ 80.71.106.0/24256FASTNETFASTNETASSIGNED PAOct 17, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.107.0/298MT-GO-NORTHWAYNORTHWAYASSIGNED PAOct 18, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.107.8/298MT-GO-RIALRIALASSIGNED PAOct 18, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.107.16/2816MT-GO-NORTHWAYNORTHWAYASSIGNED PAOct 18, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.107.32/2732MT-GO-MSCMSCASSIGNED PAOct 18, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.107.64/2664MT-GO-STCSTCASSIGNED PAOct 18, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.107.220/304MT-GO-MIFFYMIFFYASSIGNED PAOct 18, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.107.224/2816MT-GO-SAMMY_GROUPSammy GroupASSIGNED PAOct 18, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.107.240/2816MT-GO-PHILIP_TOLEDOPhilip ToledoASSIGNED PAOct 18, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.108.0/24256ELECSELECSASSIGNED PAOct 17, 2011abuse@go.com.mt
via MT-GO-20010607
└ 80.71.109.0 - 80.71.110.255512Terranet3terra software developmentASSIGNED PASep 3, 2010abuse@go.com.mt
via MT-GO-20010607
└ 80.71.111.0/24256Shireburnshireburn software developmentASSIGNED PASep 3, 2010abuse@go.com.mt
via MT-GO-20010607

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

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

4,096 addresses
TypeAddressesShareRanges
Residential3,62889%5
Hosting2566.3%1
Business2125.2%10

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jul 2010 · 16 yr
Origin networks
2
Last change of origin
Jul 2010
Recorded history

History

Handoffs
1