Core Entity Brief
- Entity: Rahkar-Pardazesh-Khavarmianeh
- Region: Iran
- Category: Network-related institution
- Primary Domain: Infrastructure
Company Briefing / Network-related institution
Rahkar-Pardazesh-Khavarmianeh
Rahkar Pardazesh Khavarmianeh matters where websites and hosted workloads rely on a small, concentrated Tehran-based hosting and routing surface. Because all observable services depend on one prefix and one observed upstream, changes in BGP origin, upstream reachability, DNS placement, RPKI or IRR state, registry attribution, or abuse-contact routing can simultaneously affect whether tens or hundreds of hosted domains resolve, route, get filtered, or are correctly attributed by network and security operators.
Evidence Pack
Primary-source references used for classification and impact scoring.
Context
Rahkar Pardazesh Khavarmianeh matters where websites and hosted workloads rely on a small, concentrated Tehran-based hosting and routing surface. Because all observable services depend on one prefix and one observed upstream, changes in BGP origin, upstream reachability, DNS placement, RPKI or IRR state, registry attribution, or abuse-contact routing can simultaneously affect whether tens or hundreds of hosted domains resolve, route, get filtered, or are correctly attributed by network and security operators.
Core Entity Brief
Signal Map
Signal Map
- Why tracked: Rahkar Pardazesh Khavarmianeh matters where websites and hosted workloads rely on a small, concentrated Tehran-based hosting and routing surface. Because all observable services depend on one prefix and one observed upstream, changes in BGP origin, upstream reachability, DNS placement, RPKI or IRR state, registry attribution, or abuse-contact routing can simultaneously affect whether tens or hundreds of hosted domains resolve, route, get filtered, or are correctly attributed by network and secur
- Object role: The company appears as a web-hosting and domain-registration provider, selling shared, WordPress, VPS, dedicated, and WooCommerce hosting services primarily through its ServerClick brand. Its public internet presence is defined by RIPE-registered autonomous system AS212063, the 87.107.172.0/24 Tehran data-center block, and DNS infrastructure on that block; this network surface serves as the foundation for all its customer-facing services.
- Impact note: Any disruption to the 87.107.172.0/24 route—whether from upstream policy changes, route-leak or hijack events, or loss of RPKI/ROA validity—would likely affect all hosted domains on that block, as the footprint is compact. Similarly, a change in the AS51431 relationship or a reputational blocklisting of the single prefix would have concentrated customer impact. The current DNS placement on that same block means that authoritative name service may fail alongside web reachability during a routing
- Control surface: network resources, registry records, operator-published service surface, relationship events
- Key dependencies: public registries, routing visibility, operator-published records