RAHKAR PARDAZESH KHAVARMIANEH PJSC is a public intelligence profile built from public registry, operator, and source material. It summarizes what can be verified about the subject, separates public infrastructure facts from private relationship claims, and keeps contact handling behind the appropriate membership tier. The profile should be read as a monitoring baseline future events, not as a claim that every relationship or dependency is already proven.
Rahkar Pardazesh Khavarmianeh PJSC operates in Iran's hosting market as the company behind ServerClick, providing shared, WordPress, VPS, dedicated, and WooCommerce hosting. Its network identity is anchored in RIPE records (ORG-RPKC1-RIPE), the AS212063 origin, and the 87.107.172.0/24 prefix labeled as a Tehran data center. With only one visible IPv4 prefix, no IPv6, and a single upstream, it embodies a small but highly observable infrastructure operator.
The company matters because it concentrates all visible service delivery on one autonomous system and one /24 prefix. Any routing leak, RPKI invalidation, upstream transit interruption, or registry record modification can simultaneously affect every hosted website and customer. That extreme dependency makes it a useful bellwether for network fragility in the Iranian hosting sector and a clear case of reachability risk.
The company matters because it concentrates all visible service delivery on one autonomous system and one /24 prefix. Any routing leak, RPKI invalidation, upstream transit interruption, or registry record modification can simultaneously affect every hosted website and customer. That extreme dependency makes it a useful bellwether for network fragility in the Iranian hosting sector and a clear case of reachability risk.
Rahkar Pardazesh Khavarmianeh PJSC operates in Iran's hosting market as the company behind ServerClick, providing shared, WordPress, VPS, dedicated, and WooCommerce hosting. Its network identity is anchored in RIPE records (ORG-RPKC1-RIPE), the AS212063 origin, and the 87.107.172.0/24 prefix labeled as a Tehran data center. With only one visible IPv4 prefix, no IPv6, and a single upstream, it embodies a small but highly observable infrastructure operator.
A single route leak, RPKI invalidation, upstream transit failure, or RIPE record change could partition every hosted domain on the AS212063/87.107.172.0/24 pathway. Operators and customers relying on ServerClick's infrastructure should treat this compact block as a critical dependency, because any disruption is likely to be total rather than partial.
RAHKAR PARDAZESH KHAVARMIANEH PJSC is a public intelligence profile built from public registry, operator, and source material. It summarizes what can be verified about the subject, separates public infrastructure facts from private relationship claims, and keeps contact handling behind the appropriate membership tier. The profile should be read as a monitoring baseline future events, not as a claim that every relationship or dependency is already proven.
A single route leak, RPKI invalidation, upstream transit failure, or RIPE record change could partition every hosted domain on the AS212063/87.107.172.0/24 pathway. Operators and customers relying on ServerClick's infrastructure should treat this compact block as a critical dependency, because any disruption is likely to be total rather than partial.
| 0.90–1.00 | A | High — direct sources |
| 0.75–0.89 | A/B | Strong |
| 0.55–0.74 | B/C | Medium |
| 0.35–0.54 | C/D | Weak–medium |
| 0.10–0.34 | D | Weak signal |
| 0.00–0.09 | D | Internal monitoring |
Several public sources
RAHKAR PARDAZESH KHAVARMIANEH PJSC
RAHKAR PARDAZESH KHAVARMIANEH PJSC is an Iran-based hosting operator selling services under the ServerClick brand. Its entire public routing footprint consists of a single autonomous system (AS212063) and a single /24 IPv4 prefix (87.107.172.0/24), creating extreme reachability concentration for every customer hosted on its network.
Why It Matters
A single route leak, RPKI invalidation, upstream transit failure, or RIPE record change could partition every hosted domain on the AS212063/87.107.172.0/24 pathway. Operators and customers relying on ServerClick's infrastructure should treat this compact block as a critical dependency, because any disruption is likely to be total rather than partial.
What Public Sources Show
RAHKAR PARDAZESH KHAVARMIANEH PJSC, operating publicly as ServerClick, is an Iranian web-hosting provider whose entire internet-facing presence hinges on a single autonomous system number and a single /24 IPv4 prefix. That extreme concentration turns any routing misconfiguration, route leak, or registry lapse into a potential full-platform outage. For the domains observed on this network—and the businesses that depend on them—the company’s footprint is not just small; it is a single point of failure.
The company appears in public routing data as AS212063, registered under ORG-RPKC1-RIPE with an allocation date of 5 January 2021. Its sole advertised prefix, 87.107.172.0/24, is described in RIPE records as the RAHKAR-DC Tehran data center block. That prefix is announced to the internet exclusively through AS51431 (Rasaneh Avabarid Private Joint Stock Company), which acts as its only visible upstream. No IPv6 addresses are currently routed, and no additional downstream providers have been observed.
Multiple independent routing intelligence platforms—bgp.tools, IPinfo, BigDataCloud, Hurricane Electric, and Cloudflare Radar—corroborate this picture consistently. They show the same AS origin, the same prefix, and the same upstream path. Registry mirrors confirm that the organisation holds a valid RPKI ROA for the prefix, and Hurricane Electric’s BGP toolkit reports the route as IRR-valid and ROA-signed. Business directories such as IranTalent and WHTop add a service layer: ServerClick is portrayed as a Tehran-based hosting company offering shared, WordPress, VPS, dedicated, and WooCommerce hosting, along with domain registration. However, these sources do not provide verifiable corporate registrations, audited financials, or named executives.
The operational control surface for Rahkar is therefore narrow and publicly visible. The RIPE records for ORG-RPKC1-RIPE, the AS212063 aut-num and route objects, and the inetnum for 87.107.172.0/24 are the primary identity and authorization levers. The ServerClick website, its nameservers, and the hosted domains themselves constitute the service layer that readers can observe. Changes to any of these—a modified route object, a shifted nameserver, a new RIPE maintainer—would directly affect the availability of hosted services. Moreover, because the company’s routing policy relies on a single upstream in AS51431, any alteration in that transit relationship would immediately be reflected in BGP monitoring.
Observers should track several concrete signals. First, confirm that AS212063 continues to originate 87.107.172.0/24 and that the RPKI ROA remains valid and matches the announced prefix. Second, monitor the upstream adjacency with AS51431; a change or loss of this neighbor would indicate a transit renegotiation or outage. Third, watch the RIPE organisation and aut-num records for any modifications to maintainer, abuse contact, or sponsor. Fourth, follow ServerClick’s DNS and hosted domain concentration; if nameservers begin pointing to IP space outside the 87.107.172.0/24 block, it would signal a migration or partnership change. Because the footprint is so small, even a single new prefix appearance would be notable.
What cannot be gleaned from public routing data is the company’s internal structure. No Iranian corporate‑registry filing has been located in the materials reviewed, so ownership, true employee count, revenue, and facility ownership remain unconfirmed. The evidence assembled here comes from registry RDAP and WHOIS records, bgp.tools, IPinfo, BigDataCloud, Cloudflare Radar, Hurricane Electric, IP2Location, IranTalent, and WHTop. These sources collectively provide a reliable network‑identity baseline, but business claims derived from directories should be treated as contextual rather than definitive until corroborated by official corporate filings or first‑party operator statements.
Operating Surface
Rahkar Pardazesh Khavarmianeh PJSC operates in Iran's hosting market as the company behind ServerClick, providing shared, WordPress, VPS, dedicated, and WooCommerce hosting. Its network identity is anchored in RIPE records (ORG-RPKC1-RIPE), the AS212063 origin, and the 87.107.172.0/24 prefix labeled as a Tehran data center. With only one visible IPv4 prefix, no IPv6, and a single upstream, it embodies a small but highly observable infrastructure operator.
The company matters because it concentrates all visible service delivery on one autonomous system and one /24 prefix. Any routing leak, RPKI invalidation, upstream transit interruption, or registry record modification can simultaneously affect every hosted website and customer. That extreme dependency makes it a useful bellwether for network fragility in the Iranian hosting sector and a clear case of reachability risk.
Watchpoints
Rahkar's operational exposure is amplified by its tiny network footprint; any single routing or registry event can cascade into a full platform outage. This concentration makes the company a leading indicator for Iran's small hosting provider stability and a clear example of dependency risk in internet infrastructure.
Key watchpoints include: (1) AS212063 route visibility, RPKI validity, and prefix origination status for 87.107.172.0/24; (2) presence and stability of upstream AS51431; (3) RIPE organisation, aut-num, and inetnum record modifications; (4) ServerClick DNS/nameserver placement shifts; (5) emergence of any additional IPv4 prefixes or IPv6 addresses.
No Iranian corporate-registry filing for Rahkar has been located, so shareholder, officer, and ownership data remain absent. There is no extractable first-party ServerClick company text, leaving the current service catalogue dependent on directory sources. Audited revenue, customer numbers, and facility ownership are unverified. Registry person handles should not be mistaken for executive identity.
Sources
- Registry RDAP / WHOIS record - public-source identity and registry context for RAHKAR PARDAZESH KHAVARMIANEH PJSC.
- bgp.tools - bgp.tools shows RAHKAR PARDAZESH KHAVARMIANEH PJSC as AS212063, registered to ORG-RPKC1-RIPE, active under RIPE, with one IPv4 prefix, zero IPv6 prefixes, upstream AS51431 and RIPE-sourced aut-num details.
- ipinfo.io - IPinfo's 87.107.172.0/24 page identifies AS212063 and RAHKAR PARDAZESH KHAVARMIANEH PJSC, shows domain serverclick.com, registry RIPE, ID RAHKAR-DC, reproduces RIPE WHOIS details and reports hosted domains on the ASN.
- irantalent.com - IranTalent describes ServerClick as a web-hosting company owned by Rahkar Pardazesh Khavarmiane, located in Tehran, with 10 to 49 employees and hosting products including shared, WordPress, VPS, dedicated, WooCommerce and dedicated-server services.
- whtop.com - WHTop lists Server Click as a Persian-language hosting provider with web-hosting and domain-registration services and shows serverclick.com DNS hostnames resolving partly to Rahkar Pardazesh Khavarmianeh Tehran Data Center addresses.
- radar.cloudflare.com - Cloudflare Radar identifies AS212063 as Rahkar-Pardazesh-Khavarmianeh in Iran and exposes public traffic, routing, announced address space and BGP-announcement views for the AS.
- ip2location.com - IP2Location lists AS212063 as Rahkar Pardazesh Khavarmianeh PJSC, country Iran, domain serverclick.com, total IPv4 address count 256, netblock 87.107.172.0/24 and upstream AS51431.
- ipinfo.io - IPinfo identifies AS212063 as RAHKAR PARDAZESH KHAVARMIANEH PJSC, associates it with serverclick.com, classifies it as hosting, and reports 256 IPv4 addresses, no IPv6 addresses, hosted-domain telemetry, AS51431 as peer/upstream and no downstreams.
- bigdatacloud.com - BigDataCloud corroborates AS212063 as Rahkar-Pardazesh-Khavarmianeh / RAHKAR PARDAZESH KHAVARMIANEH PJSC, with 256 IPv4 addresses, one IPv4 prefix, zero IPv6 prefixes, RIPE registry, registration date 2021-01-05, last change 2023-05-03 and AS51431 as receiving-from ASN.
- bgp.he.net - Hurricane Electric's BGP page for 87.107.172.0/24 identifies AS212063 as the origin and RAHKAR PARDAZESH KHAVARMIANEH PJSC as origin and prefix registrant, with IRR and ROA validity shown in the search-visible record.
- bigdatacloud.com - Shows 87.107.172.0/24 as a RIPE assigned, globally reachable BGP prefix, announced by AS212063 for RAHKAR PARDAZESH KHAVARMIANEH PJSC and receiving from AS51431 Rasaneh Avabarid Private Joint Stock Company.
- Registry RDAP / WHOIS record - Mirrors RIPE WHOIS details for AS212063 and 87.107.172.0/24, including ORG-RPKC1-RIPE, the Rahkar organisation name, route policy statements, prefix details and record modification dates.
Domain of operation
RAHKAR PARDAZESH KHAVARMIANEH PJSC is an Iran-based hosting operator selling services under the ServerClick brand. Its entire public routing footprint consists of a single autonomous system (AS212063) and a single /24 IPv4 prefix (87.107.172.0/24), creating extreme reachability concentration for every customer hosted on its network.
- Registry RDAP / WHOIS record: public-source identity and registry context for RAHKAR PARDAZESH KHAVARMIANEH PJSC. Evidence basis: source-d6e3f6e44322
Timeline
- RAHKAR PARDAZESH KHAVARMIANEH PJSC public evidence observed
The company matters because it concentrates all visible service delivery on one autonomous system and one /24 prefix. Any routing leak, RPKI invalidation, upstream transit interruption, or registry record modification can simultaneously affect every hosted website and customer. That extreme dependency makes it a useful bellwether for network fragility in the Iranian hosting sector and a clear case of reachability risk.
At A Glance
- Name: RAHKAR PARDAZESH KHAVARMIANEH PJSC
- Type: Internet registry
- Base: Iran
- Profile focus: Institution
What It Does
- network resources
- registry records
- operator-published service surface
- relationship events
Why It Matters
- A single route leak, RPKI invalidation, upstream transit failure, or RIPE record change could partition every hosted domain on the AS212063/87.107.172.0/24 pathway. Operators and customers relying on ServerClick's infrastructure should treat this compact block as a critical dependency, because any disruption is likely to be total rather than partial.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- public registries
- routing visibility
- operator-published records
Track verified source updates, role changes, and current public evidence.
A single route leak, RPKI invalidation, upstream transit failure, or RIPE record change could partition every hosted domain on the AS212063/87.107.172.0/24 pathway. Operators and customers relying on ServerClick's infrastructure should treat this compact block as a critical dependency, because any disruption is likely to be total rather than partial.
Longer-term relevance depends on verified operating, policy, and relationship changes.
Member Briefing
Deeper Profile Context
Login is required to unlock the full profile briefing and source notes.
Only for Strategy Circle
Strategic Circle Access
Open to all readers. Unlock profile briefings after joining and logging in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance Access
For owners and management of IP-holding companies. Login required to unlock.
Join Leadership AlliancePublic View
A single route leak, RPKI invalidation, upstream transit failure, or RIPE record change could partition every hosted domain on the AS212063/87.107.172.0/24 pathway. Operators and customers relying on ServerClick's infrastructure should treat this compact block as a critical dependency, because any disruption is likely to be total rather than partial.
Watchpoints
- Rahkar's operational exposure is amplified by its tiny network footprint; any single routing or registry event can cascade into a full platform outage.
- This concentration makes the company a leading indicator for Iran's small hosting provider stability and a clear example of dependency risk in internet infrastructure.
- Key watchpoints include: (1) AS212063 route visibility, RPKI validity, and prefix origination status for 87.107.172.0/24; (2) presence and stability of upstream AS51431; (3) RIPE organisation, aut-num, and inetnum record modifications; (4) ServerClick DNS/nameserver placement shifts; (5) emergence of any additional IPv4 prefixes or IPv6 addresses.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track RAHKAR PARDAZESH KHAVARMIANEH PJSC?
The company matters because it concentrates all visible service delivery on one autonomous system and one /24 prefix. Any routing leak, RPKI invalidation, upstream transit interruption, or registry record modification can simultaneously affect every hosted website and customer. That extreme dependency makes it a useful bellwether for network fragility in the Iranian hosting sector and a clear case of reachability risk.
What evidence supports the profile?
public-source identity and registry context for RAHKAR PARDAZESH KHAVARMIANEH PJSC.
What should readers watch next?
Rahkar's operational exposure is amplified by its tiny network footprint; any single routing or registry event can cascade into a full platform outage.





