Data as of Nov 20, 2026

185.129.62.0/23

3 anonymizer addresses · 0.59% · Tor exit3 residential-proxy exits · 30 days

Zencurity ApS

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
>99% of it

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

624 observations
IPv4 market

Path

1 · Holder
record created Nov 30, 2015
2 · Leased from
not leased
3 · Announced by
AS57860 Zencurity ApS
since Jan 2022 · 4.8 yr ago
4 · Use
named Tor
Business

Operators, sellers and brokers

Tor

NameParentIn 185.129.62.0/23/24s
TorThe Tor Project
30.59%
1

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

185.129.62.0/23

From the registry to its use

  1. Nov 30, 2015
    Registry record
    Zencurity ApS
    ALLOCATED PA
    185.129.60.0/22
  2. Sep 16, 2021
    Route object
    AS57860 Zencurity ApS
    RIPE route object for AS57860 Zencurity ApS, maintainer DK-ZENCURITY-1-MNT
  3. Jan 28, 2022– today
    Announced
    AS57860 Zencurity ApS
    Business
  4. today
    Used
    Tor
    Tor

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
185.129.60.0/221,024DK-ZENCURITY-20151130Zencurity ApS (ORG-ZA135-RIPE) · DKALLOCATED PANov 30, 2015abuse@zencurity.dk
└ 185.129.62.0/24256SERVICE-NET1Various servers including Tor serversASSIGNED PADec 17, 2015abuse@zencurity.dk
via DK-ZENCURITY-20151130
└ 185.129.63.0/25128PYJAMAS01Pyjamas fun networkASSIGNED PANov 23, 2022abuse@zencurity.dk
via DK-ZENCURITY-20151130

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

512 addresses
TypeAddressesShareRanges
Business509>99%2
Tor exitanonymizer30.59%3

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2022
Current origin since
Jan 2022 · 4.8 yr
Origin networks
1