RED-DRAGONFLY-NETBAR — IP ranges & network footprint

IP Ranges (2)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
122.225.123.120/30	RED-DRAGONFLY-NETBAR	APNIC	ASSIGNED NON-PORTABLE	● high
61.158.35.128/27	RED-DRAGONFLY-NETBAR	APNIC	ASSIGNED NON-PORTABLE	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “RED DRAGONFLY” — 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.

RED-DRAGONFLY 1 blocks

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.

Blue Dragonfly Netbar via CNCGROUP IP network of ShangHai IDC sub-allocation
Dragonfly via Vodafone Romania S.A. sub-allocation
DRAGONFLY_SHIPPING_NL_BV via Vodafone Libertel B.V. sub-allocation
Dragonfly Net Bar via No.31,Jin-rong Street sub-allocation
BLUEDRAGONFLY-CLUB via CNCGROUP IP network of ShangHai IDC sub-allocation
Red Dragonfly Netbar via No.31,Jin-rong Street sub-allocation
Red Dragonfly Netbar via No.31,Jin-rong Street sub-allocation
Dragonfly Netbar via CNCGROUP IP network of ShangHai IDC sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

BG63-AP BG63-AP CH119-AP MAINT-CN-CHINANET-ZJ-HU MAINT-CNCGROUP-HL XQ319-AP

Netblocks	2
All fragments	3 blocks across 2 clusters
Cluster ID	212628620
Registry	APNIC
Customers	find customers using this network →

Attribution	BGP parent (inherited)
Shared handles	clustered on 6 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works