Data as of Nov 17, 2026

185.231.33.0/24

1 anonymizer address · 0.39% · Tor exit2 residential-proxy exits · 30 days

Datashield, Inc.

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

661 observations
  • Tor exit · anonymizer
  • Hosting
IPv4 market

Path

1 · Holder
record created Nov 9, 2017
2 · Leased from
not leased
3 · Announced by
AS211720 Datashield, Inc.
since Aug 2025 · 15 mo ago
4 · Use
named Tor
Hosting

Operators, sellers and brokers

Tor

NameParentIn 185.231.33.0/24/24s
TorThe Tor Project
10.39%
1

Lineage

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

185.231.33.0/24

From the registry to its use

  1. Nov 9, 2017
    Registry record
    Datashield, Inc.
    ALLOCATED PA
    185.231.32.0/22
  2. Dec 16, 2020– Feb 8, 2022
    Announced
    AS57724 Ddos-Guard Ltd
    Hosting
  3. Jul 4, 2025
    Route object
    AS211720 Datashield, Inc.
    RIPE route object for AS211720 Datashield, Inc., maintainer DATASHIELD-MNT
  4. Aug 4, 2025– today
    Announced
    AS211720 Datashield, Inc.
    Hosting
  5. 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.231.32.0/221,024SC-DATASHIELD-20171109Datashield, Inc. (ORG-DI60-RIPE) · SCALLOCATED PANov 9, 2017abuse@xor.sc
└ 185.231.33.0/24256SC-DATASHIELD-04072025unknownASSIGNED PAJul 4, 2025abuse@xor.sc
via SC-DATASHIELD-20171109

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

256 addresses
TypeAddressesShareRanges
Hosting255>99%2
Tor exitanonymizer10.39%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Reactivated
First seen
Dec 2020
Current origin since
Aug 2025 · 1.3 yr
Origin networks
2
Last change of origin
Aug 2025
Recorded history

History

Handoffs
1