YAZDTELECOM
Data as of 2026-08-09
BGP inherited
Cluster stats
| Netblocks | 4 · 856 IPv4 addresses |
| Cluster ID | 220353591 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2.184.32.0/23 | YAZDTELECOM | RIPE | ASSIGNED PA | ● low |
| 78.39.84.192/26 | YAZDTELECOM | RIPE | ASSIGNED PA | ● low |
| 78.39.85.0/24 | YAZDTELECOM | RIPE | ASSIGNED PA | ● low |
| 85.185.158.64 – 85.185.158.87 | YAZDTELECOM | RIPE | SUB-ALLOCATED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (2)
These blocks are registered to YAZDTELECOM 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.
| 2.184.32.0/23 /23 | authorized for AS58224 — Iran Telecommunication Company PJS |
| 78.39.85.0/24 /24 | authorized for AS58224 — Iran Telecommunication Company PJS |
NIC Handles
AS12880-MNT
DUMY-RIPE
DUMY-RIPE
TCI-RIPE-MNT