htp GmbH

HTP-CHRISTMANN

BGP inherited

Cluster stats

Netblocks	6
All fragments	7 blocks across 2 clusters
Cluster ID	209616762
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

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

Footprint over time

5 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
81.14.168.144/28	HTP-CHRISTMANN	RIPE	ASSIGNED PA	● low
81.14.179.64/29	HTP-CHRISTMANN	RIPE	ASSIGNED PA	● low
81.14.179.96/27	HTP-CHRISTMANN	RIPE	ASSIGNED PA	● low
81.14.182.32/27	HTP-CHRISTMANN	RIPE	ASSIGNED PA	● low
81.14.186.0/27	HTP-CHRISTMANN	RIPE	ASSIGNED PA	● low
81.14.204.32/29	HTP-CHRISTMANN	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

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

HTP-Christmann_Informationstechnik 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.

LASSE-CHRISTMANN-NET via TDC Holding A/S sub-allocation
Christmann Caroline via Orange S.A. sub-allocation
Christmann via PFALZKOM GmbH sub-allocation
Christmann Informationstechnik via htp GmbH sub-allocation
HTP6-CHRISTMANN via htp GmbH sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HTP-MNT