MARYKAY

BGP inherited
Cluster stats
Netblocks7
Registered in KZ (3) · Portugal (2) · China (1) · Russia (1)
All fragments 13 blocks across 5 clusters
Cluster ID209064906
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
61.152.251.155 – 61.152.251.158 Marykay_LTD APNIC ASSIGNED NON-PORTABLE ● low
89.218.27.12/30 MARYKAY RIPE ASSIGNED PA ● low
89.218.27.16/30 MARYKAY RIPE ASSIGNED PA ● low
195.23.45.192/29 MARYKAY RIPE ASSIGNED PA ● low
195.23.61.192/29 MARYKAY RIPE ASSIGNED PA ● low
212.154.176.80/29 MARYKAY RIPE ASSIGNED PA ● low
212.176.1.56/29 MARYKAY-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MARYKAY” — 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.
  • Marykay Ba via SWAN, a.s. sub-allocation
  • marykay-ua via "SCIENTIFIC-INDUSTRIAL FIRM "VOLZ" LIMITED LIABILITY COMPANY 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 HY174-AP IP-MNT KNIC-MNT MAINT-CHINANET-SH ROSPRINT-NCC XCM3-AP