Wael Nabhan

Wael Nabhan is listed as an admin/tech contact for AS210990 in RIPE registry data, associated with SpeedClick. The evidence is limited to two official sources: RDAP and RIPEstat. No independent biography, corporate affiliation, or routing activity is verified. The profile serves as a registry-contact bookmark; its intelligence value lies in detecting future changes. Key uncertainties include whether Nabhan is currently employed, his real technical authority, and the operational status of AS210990. Watchpoints include registry record changes, new prefix announcements, and any public professional profile.

Wael Nabhan

Wael Nabhan is publicly listed in RIPE registry data as the administrative and technical contact for autonomous system AS210990 (SP-HOSTING-AS), which is registered to SpeedClick for Information Technology and Communication Ltd. No independent biography, current employment verification, or routing activity beyond the registry snapshot is available; the profile serves as a low-confidence observable for monitoring changes in stewardship of the autonomous system.

Why It Matters

As a publicly listed contact, Wael Nabhan acts as a touchpoint for operators, researchers, and registry officials who need to escalate issues involving AS210990. A material change in this record would shift the mapping of operational responsibility and may reveal broader organisational shifts, impacting how network resources are tracked and risk-assessed.

What Public Sources Show

Wael Nabhan appears in RIPE registry data as the administrative and technical contact for autonomous system AS210990, an entry named SP-HOSTING-AS and registered to SpeedClick for Information Technology and Communication Ltd. The public record is limited to this registry snapshot, with no independent biography or current employment confirmation.

For infrastructure analysts, Nabhan serves as a low-confidence observable: any change in the contact data could signal shifts in the stewardship of the autonomous system or restructuring at SpeedClick.

The RDAP record accessed through rdap.org ties Wael Nabhan to admin and tech roles for AS210990. A separate RIPEstat overview confirms the ASN exists but does not provide active routing data. Another individual, Mahmoud Alhabbash, shares the same admin and tech roles, suggesting responsibilities may be distributed.

The abuse contact listed in the record points to SpeedClick, not to Nabhan directly, underscoring that the contact role is operational rather than personal ownership.

The contact role, in RIPE policy, includes maintaining accurate registry entries and being a public point of contact for operational queries or policy matters related to the ASN. There is no public evidence that Nabhan controls routing policies, makes business decisions, or holds executive authority. The control surface is narrow: the ability to update ASN registration details and respond to inquiries through RIPE procedures.

Analysts tracking internet number resources can use Wael Nabhan’s contact listing as a signal point. If the RDAP record changes—for example, Nabhan is replaced or the organisation fields are modified—it could indicate a sale, restructuring, or reassignment of administrative duties. This makes the contact a useful, albeit low-confidence, indicator for monitoring the governance of AS210990 and the operational health of SpeedClick’s internet resources.

No public biography, LinkedIn profile, or company staff page verifies Wael Nabhan’s current title, employer, or location. The only verifiable detail is the RIPE handle WN791-RIPE, which lacks a biographical entry. The absence of active prefix announcements or routing data in the provided sample further limits the assessment to the ASN’s existence. The contact may be stale, shared, or automated, and the real-world identity has not been corroborated.

What would change the public assessment? A new RDAP or WHOIS record for AS210990 showing a different contact would immediately shift the baseline. The emergence of prefix announcements from AS210990 would add operational weight. A professional profile, public presentation, or company page naming Nabhan would provide missing biographical verification. Finally, any public change involving SpeedClick’s organisation or Mahmoud Alhabbash’s role could also affect the interpretation.

Until more recent or richer evidence surfaces, Wael Nabhan remains a registry-contact bookmark. The intelligence value lies in detecting change, not in asserting personal control or influence. Readers should treat the contact as a public record entry—accurate at the time of snapshot but requiring ongoing verification—and watch for signals that would raise its significance from a simple contact role to something more operationally material.

Operating Surface

The contact role, as defined by RIPE policy, involves maintaining accurate registry data for AS210990 and acting as a public point of contact for operational and policy inquiries. The role is limited to this registry context, without confirmed executive authority, budget control, or hands-on network engineering responsibilities. Another individual, Mahmoud Alhabbash, shares the same admin and tech contact roles.

Infrastructure analysts monitoring internet number resources can use Wael Nabhan's registry listing to detect changes in the governance of AS210990. Any alteration in the RDAP record—such as a new contact name or updated organisation—could signal a sale, restructuring at SpeedClick, or reassignment of administrative duties. The contact provides a low-cost early indicator when corroborated with routing or corporate evidence.

Watchpoints

Wael Nabhan is a low-cost registry-contact signal with no verified real-world activity. The primary strategic value is as an early indicator of organisational change when combined with routing data or corporate records. Until more evidence emerges, the contact carries minimal operational weight.

Monitor the RDAP record for AS210990 monthly for changes. Set up alerts for any prefix announcements from the ASN. Regularly search for Wael Nabhan on professional networks. Any confirmed appearance at industry events or in company communications would require re-evaluation.

No verified biography, employer page, or public profile exists beyond the registry. Active prefix routing data is missing. The business nature and operational scale of SpeedClick are unverified. Independent corroboration of the contact's current role and the ASN's operational footprint is needed.

Sources

• Registry RDAP / WHOIS record - public-source identity and registry context for Wael Nabhan.
• RIPE registry record - RIPEstat provides a public overview page for AS210990, supporting that the ASN exists as a publicly visible network resource identifier.