Itm8 A/S — IP ranges & network footprint

IP Ranges (2)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
185.193.122.128/29	DK-ITM8-CUST00114	RIPE	ASSIGNED PA	● low
2a03:1100:10:200::/56	DK-ITM8-CUST00114	RIPE	ASSIGNED	● low

IPv6 ranges (1)

CIDR
2a03:1100:10:200::/56

Possibly related to this organisation

what's this?

Same name family

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

Combined view of all 20 name-family clusters →

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.

Itm8 Cust00105 via Itm8 A/S sub-allocation
Itm8 Cust00106 via Itm8 A/S sub-allocation
Cust Humac via Itm8 A/S sub-allocation
Cust Helm via Itm8 A/S sub-allocation
Cust Baagoe Schou via Itm8 A/S sub-allocation
Cust Aau via Itm8 A/S sub-allocation
Cust Karakternet via Itm8 A/S sub-allocation
Cust Bisnode via Itm8 A/S 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

DUMY-RIPE DUMY-RIPE ITM8-MNT

Netblocks	2
IPv6	1 prefix (largest 2a03:1100:10:200::/56)
All fragments	25 blocks across 20 clusters
Cluster ID	216098674
Registry	RIPE
Customers	find customers using this network →

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