Data as of Nov 16, 2026

185.130.44.0/24

No anonymizer space · no proxy exits in 30 days

Privex Inc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

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.130.44.0/221,024BZ-PRIVEX-20181011Privex Inc. (ORG-PI82-RIPE) · BZALLOCATED PAOct 11, 2018abuse@privex.io
└ 185.130.44.0/24256PRIVEX_SEPrivex Sweden NetworkLIR-PARTITIONED PANov 1, 2018abuse@privex.io
via BZ-PRIVEX-20181011
└ 185.130.44.0/2732PRIVEX_INTERNAL_SE1Privex Internal Services SwedenASSIGNED PANov 1, 2018abuse@privex.io
via PRIVEX_SE
└ 185.130.44.69/321Privex_SeunknownASSIGNED PAFeb 25, 2022abuse@privex.io
via PRIVEX_SE
└ 185.130.44.102/321PRIVEX_CUSTOMER_TOR_EXIT1unknownASSIGNED PAAug 13, 2019abuse@privex.io
via PRIVEX_SE
└ 185.130.44.108/321PRIVEX_TOR_EXIT_SE1unknownASSIGNED PAAug 13, 2019abuse@privex.io
via PRIVEX_SE
└ 185.130.44.124/321PRIVEX_TOR_EXIT_CUST1_SE1unknownASSIGNED PAJan 11, 2021abuse@privex.io
via PRIVEX_SE

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
Oct 2018
Current origin since
Oct 2018 · 8.1 yr
Origin networks
1