Paw Host

PawHost
Registry
Cluster stats
Netblocks6
All fragments 8 blocks across 3 clusters
Cluster ID211730029
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.155.15/32 PawHost PEERINGDB ASSIGNED ● high
185.1.166.29/32 PawHost PEERINGDB ASSIGNED ● high
2001:7f8:f2:e1:0:21:4915:1/128 PawHost PEERINGDB ASSIGNED ● high
2a0c:b641:701::21:4915:1/128 PawHost PEERINGDB ASSIGNED ● high
2a06:1283:d000::/40 PawHost RIPE ALLOCATED-BY-LIR ● low
2a0f:b240:4::/46 Pawhost RIPE ALLOCATED-BY-LIR ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PawHost” — 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.

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
Possible discrepancies (2)

These blocks are registered to PawHost but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a06:1283:d000::/40 /40 authorized for AS214915 — Jan Smyrek
2a0f:b240:4::/46 /46 authorized for AS214915 — Jan Smyrek

NIC Handles

AS214915 DUMY-RIPE DUMY-RIPE FPS-Server-MNT GOCODEIT-AUTO-MNT GOCODEIT-MNT Host-Array-MNT PawHost-MNT