Selhoz

SELHOZ

Registry

Cluster stats

Netblocks	7
All fragments	18 blocks across 9 clusters
Cluster ID	210476743
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	Registry record
Shared handles	clustered on 3 shared RIR contact/maintainer handles
Registry names	2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-13

IP Ranges (7)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
5.63.71.180/30	SELHOZ	RIPE	ASSIGNED PA	● low
84.240.230.168/30	Selhoz	RIPE	ASSIGNED PA	● low
89.218.226.76/30	Selhoz	RIPE	ASSIGNED PA	● low
89.218.248.128/30	SELHOZ	RIPE	ASSIGNED PA	● low
92.46.48.180/30	SELHOZ	RIPE	ASSIGNED PA	● low
92.47.148.244/30	SELHOZ	RIPE	ASSIGNED PA	● low
95.58.46.140/30	SELHOZ	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “SELHOZ” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

SELHOZECONOM via Nets and Services JCS sub-allocation
SELHOZ-ACADEMY via PJSC Rostelecom sub-allocation
Sovintel Msk Rosselhozbank sub-allocation
POL-DALSELHOZTORG-NET via PJSC Rostelecom sub-allocation
ROS-SELHOZ-BANK via PJSC Rostelecom sub-allocation
Min Selhoz Amur via PJSC Rostelecom sub-allocation
Min_Selhoz_Perm via PJSC Rostelecom sub-allocation
Rosselhoznadzor_sib via PJSC Rostelecom sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT