Paw Host

PawHost
Data as of 2026-10-11
Registry
This organisation
Netblocks8
IPv6 5 prefixes (largest 2a06:1283:d000::/40)
Also registered under this name 10 netblocks across 3 separate records
Record ID245978210
RegistryPEERINGDB
Customerssee who runs inside 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 · report an issue

IP Ranges (8)

⬇ 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
185.1.170.82/32 PawHost PEERINGDB ASSIGNED ● high
2001:7f8:9e:0:3:4783:0:1/128 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

IPv6 ranges (5)

CIDR
2a06:1283:d000::/40
2a0f:b240:4::/46
2001:7f8:9e:0:3:4783:0:1/128
2001:7f8:f2:e1:0:21:4915:1/128
2a0c:b641:701::21:4915:1/128

Footprint over time

5 weekly snapshots · JSON
8 +2 netblocks since 2026-07-13
2026-07-13 peak 8 2026-10-11

Network trust

what's this?
RPKI hygiene: B how networks compare →
87.5% of checked blocks have valid RPKI ROA coverage (7 of 8)
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