Data as of Nov 13, 2026

185.166.253.0/24

Anonymizer · Datacenter proxy

web2objects GmbH

Announcement
this exact prefix
No RPKI
Announced by
Type
Datacenter proxy
Risk
85 / 100 · Critical
IPv4 market

Path

1 · Holder
record created Apr 8, 2022
2 · Leased from
not leased
3 · Announced by
AS204646 web2objects GmbH
since Jun 2023 · 3.4 yr ago
4 · Use
Datacenter proxy
anonymizer space, operator not named

Lineage

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

185.166.253.0/24

From the registry to its use

  1. Jan 27, 2020– Feb 19, 2020
    Announced
    AS61317 Hivelocity LLC
    Hosting
  2. Feb 8, 2020– Sep 17, 2021
    Announced
    AS262287 Latitude.sh LTDA
    Hosting
  3. Feb 18, 2020
    Route object
    AS262287 Latitude.sh LTDA
    RADB route object for AS262287 Latitude.sh LTDA, maintainer MAINT-AS262287
  4. Apr 8, 2022
    Registry record
    web2objects GmbH
    ALLOCATED PA
    185.166.253.0/24
  5. Jun 28, 2023– today
    Announced
    AS204646 web2objects GmbH
    Hosting
  6. Jul 1, 2023
    Route object
    AS204646 web2objects GmbH
    RIPE route object for AS204646 web2objects GmbH, maintainer W2O-MNT

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.166.253.0/24256DE-WEB2OBJECTS-20200116web2objects GmbH (ORG-WG52-RIPE) · DEALLOCATED PAApr 8, 2022abuse@web2objects.de
└ 185.166.253.32/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.48/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.64/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.80/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.96/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.112/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.128/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.144/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.160/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.176/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.192/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.208/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.224/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116
└ 185.166.253.240/2816VPN-Consumer-NetworkunknownASSIGNED PAJan 23, 2020abuse@web2objects.de
via DE-WEB2OBJECTS-20200116

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
Reactivated
First seen
Jan 2020
Current origin since
Jun 2023 · 3.4 yr
Origin networks
3
Last change of origin
Jun 2023
Recorded history

History

Handoffs
2