Core Entity Brief
| Entity | Mohammadreza Gholami |
|---|---|
| Public role | Accurate WHOIS/RDAP information is critical for network troubleshooting and abuse reporting. If Gholami’s contact data is incorrect or unreachable, it can delay incident response or misdirect abuse reports. While the ASN is dormant, future routing activity could increase his operational significance, making this a watchpoint for any change in routing posture or registry modifications. |
| Region | RIPE NCC service region |
| Category | Individual registry-holder label |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | Quarter (30-120d) |
| Impact | Medium |
| Confidence | 0.95 |
| Evidence coverage | 2 public source references |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 02, 2026 |
Mohammadreza Gholami is an individual registry contact, not a company; his public profile is limited to his role for AS215351.
What It Does
- Operational role: He acts as administrative and technical contact for AS215351; there is no evidence of a revenue-generating business model or customer-facing operation.
Operating Snapshot
- Registry context: He is listed in RIPE NCC records under handle MGAD-RIPE with direct assignment of AS215351, and no organizational entity is associated.
Control Surface
- Registry access: He can update RIPE NCC records for AS215351; there is no evidence of control over routing infrastructure or IP prefixes.
Watchpoints
- Record Changes: Any change to the RIPE NCC entry for AS215351—new organization, updated contacts, or expiry—would alter his public standing.
- Routing Activity: Announcement of IP prefixes by AS215351 would indicate a shift to operational use, increasing his significance.

