Data as of Nov 11, 2026

83.68.96.0/19

1 residential-proxy exit · 30 days

Sanef SA

Announcement
this exact prefix
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

1 observation

Proxy providers listing exits

  • AnyIP

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
83.68.96.0/198,192FR-SANEF-20040514Sanef SA (ORG-SDAD1-RIPE) · FRALLOCATED PAMay 14, 2004thomas.pelzer@sanef.com
└ 83.68.96.0/221,024SANEFunknownASSIGNED PANov 10, 2023thomas.pelzer@sanef.com
via FR-SANEF-20040514
└ 83.68.100.0/24256MAS-REIMSMASTERNAUTASSIGNED PAOct 3, 2005thomas.pelzer@sanef.com
via FR-SANEF-20040514
└ 83.68.101.0/2732ALPHA-REIMSALPHAMOSAASSIGNED PADec 9, 2005thomas.pelzer@sanef.com
via FR-SANEF-20040514
└ 83.68.102.0/24256TREKKPlage TREKKASSIGNED PAOct 29, 2010thomas.pelzer@sanef.com
via FR-SANEF-20040514

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

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2005
Current origin since
Jun 2005 · 21 yr
Origin networks
1