The Technical Director profile resolves to the RIPE role contact TD7104-RIPE for ONOFF TELECOM SAS. No person is verified behind the handle. The company provides cloud‑based virtual numbers via the Onoff app, operating in multiple European countries and holding RIPE NCC membership. Its control surface includes number assignment, account management, API access, and enforcement of terms. Key gaps are the absence of a named individual, missing revenue data, and a SIREN discrepancy in French numbering decisions. Watch for registry changes and active BGP announcements.
Technical Director serves as the administrative and technical contact role for AS211948 within the RIPE registry, associated with ONOFF TELECOM SAS. It has no verified personal identity, employment history, or independent authority outside that registry function.
The profile matters because it identifies the actual operating entity—ONOFF TELECOM SAS—a licensed telecom operator offering cloud‑based virtual numbers. Mistaking the role for a person misdirects attention from the company’s control over number assignment, service stability, and API reliability, which are the real dependencies for users and businesses.
The profile matters because it identifies the actual operating entity—ONOFF TELECOM SAS—a licensed telecom operator offering cloud‑based virtual numbers. Mistaking the role for a person misdirects attention from the company’s control over number assignment, service stability, and API reliability, which are the real dependencies for users and businesses.
Technical Director serves as the administrative and technical contact role for AS211948 within the RIPE registry, associated with ONOFF TELECOM SAS. It has no verified personal identity, employment history, or independent authority outside that registry function.
Users and businesses depend on ONOFF’s ability to assign numbers, keep calls reachable, suspend accounts, and expose business APIs. Disruption or misuse of these controls can interrupt communications and business operations. Treating the registry role as a person instead of a company contact obscures where accountability sits.
The Technical Director profile resolves to the RIPE role contact TD7104-RIPE for ONOFF TELECOM SAS. No person is verified behind the handle. The company provides cloud‑based virtual numbers via the Onoff app, operating in multiple European countries and holding RIPE NCC membership. Its control surface includes number assignment, account management, API access, and enforcement of terms. Key gaps are the absence of a named individual, missing revenue data, and a SIREN discrepancy in French numbering decisions. Watch for registry changes and active BGP announcements.
Users and businesses depend on ONOFF’s ability to assign numbers, keep calls reachable, suspend accounts, and expose business APIs. Disruption or misuse of these controls can interrupt communications and business operations. Treating the registry role as a person instead of a company contact obscures where accountability sits.
| 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
Technical Director
The ‘Technical Director’ label in public internet registry records is a RIPE role contact (TD7104-RIPE), not a verified individual. It is tied to ONOFF TELECOM SAS, a Paris‑based cloud telecom operator that provides virtual phone numbers under the Onoff brand. The profile surfaces the real entity behind the label to prevent misattribution of operational control.
Why It Matters
Users and businesses depend on ONOFF’s ability to assign numbers, keep calls reachable, suspend accounts, and expose business APIs. Disruption or misuse of these controls can interrupt communications and business operations. Treating the registry role as a person instead of a company contact obscures where accountability sits.
What Public Sources Show
The ‘Technical Director’ label in public internet‑registry records is a RIPE role contact (TD7104‑RIPE), not a verified individual. It acts as the administrative and technical contact for AS211948, which is registered to ONOFF TELECOM SAS. Treating the role as a person risks misattributing operational control to a phantom entry instead of the real telecom operator behind the service.
ONOFF TELECOM SAS is a Paris‑based cloud telecom operator that turns phone numbers into app‑managed resources. Its Onoff app lets consumers hold multiple mobile numbers on one smartphone without a second SIM. The business version adds a management console, API access, and webhook logging. Users and companies rely on ONOFF to assign numbers, keep calls and messages flowing, and enforce service terms.
Registry mirrors confirm AS211948 as ONOFF‑FR with TD7104‑RIPE as admin and tech contact. The company’s own terms identify the legal entity as ONOFF TELECOM SAS (Paris trade register 832 235 253). The French government’s company directory shows it active in telecommunications since 2017 with 20‑49 employees. Its help pages describe licensed operations in over 20 countries and a patented cloud‑numbering technology.
ONOFF’s control surface covers number assignment, account management, billing, API access, webhook data streams, service suspension, and enforcement of acceptable‑use policies. It also maintains the registry entries for AS211948 as a RIPE NCC member. The TD7104‑RIPE contact is merely a registry communication point; it does not represent a person with independent technical authority over the network or the company’s operations.
Revenue details are not public, but the company appears to earn through app subscriptions, in‑app purchases, and business service fees. Its Google Play listing shows over one million downloads and more than 18,000 reviews. An ARCEP decision from 2022 renewed mobile numbering resources for an entity named Onoff telecom, although the SIREN used in that decision differs from the current company, creating a legal‑continuity question that remains unconfirmed.
Two watchpoints change the profile. First, if ONOFF begins announcing IP prefixes under AS211948, its infrastructure significance rises from a pure numbering service to an active network presence. Second, any public naming of an employee alongside the TD7104‑RIPE handle would create a person‑level profile, shifting the assessment. Until then, the label stays a role contact only.
Several gaps temper the assessment. No public biography, employment record, or media quote links a named person to the title. The exact revenue model, customer count, and per‑country licensing details remain undocumented. The ARCEP SIREN mismatch means readers should verify the current corporate structure before relying on the number‑assignment history. Readers should re‑check official pages and registry records immediately before publication, as those sources change.
Operating Surface
Technical Director serves as the administrative and technical contact role for AS211948 within the RIPE registry, associated with ONOFF TELECOM SAS. It has no verified personal identity, employment history, or independent authority outside that registry function.
The profile matters because it identifies the actual operating entity—ONOFF TELECOM SAS—a licensed telecom operator offering cloud‑based virtual numbers. Mistaking the role for a person misdirects attention from the company’s control over number assignment, service stability, and API reliability, which are the real dependencies for users and businesses.
Watchpoints
ONOFF TELECOM SAS is a small but licensed European virtual‑number operator with a consumer and business split. Its strategic significance lies in the growing dependence on app‑based identity and communications, not in raw network infrastructure scale. The absence of BGP announcements under AS211948 means its footprint is currently voice/SMS‑centric, but any move into IP transit or peering would change its infrastructure profile.
Monitor RIPE and PeeringDB for prefix announcements under AS211948; any active routes would signal a shift from pure numbering services to a more traditional ISP/operator role. Also track if a named employee publicly assumes the Technical Director mantle, which would create a person‑level intelligence record. Verify the SIREN continuity with updated French trade registry excerpts.
The evidence set lacks audited financial statements, per‑country licensing certificates, a named and linked Technical Director person, and routing updates. Without these, revenue scale, regulatory standing per jurisdiction, network footprint, and human accountability remain unconfirmed.
Sources
- Registry RDAP / WHOIS record - public-source identity and registry context for Technical Director.
- Registry RDAP / WHOIS record - Mirrors RIPE WHOIS data showing AS211948 as ONOFF-FR, org ORG-OTS22-RIPE / ONOFF TELECOM SAS, and TD7104-RIPE as admin and technical contact with role Technical Director.
- support.onoff.app - Onoff states that it is a telecommunications operator based in Paris and Tallinn and that its app lets users have several phone numbers on a smartphone without a second SIM card or another mobile device.
- onoff.app - Onoff's About page states that Onoff is owned by Onoff Telecom, describes licensed country coverage, patented cloud numbering technology, offices in Paris and Tallinn, staff scale, and message volume claims.
- business.onoff.app - Onoff Business states that it belongs to Onoff Telecom and describes licensed telecom operation, number supply, patented technology, 120 people, and Paris and Tallinn offices.
- onoff.app - Onoff terms identify ONOFF TELECOM as a Paris registered SAS under number 832 235 253 and describe the ONOFF application as secondary contact management and communication services.
- business.onoff.app - Onoff Business terms define company accounts, management console, mobile numbers, credits, services, WebApp, subscriptions, and business payment obligations.
- play.google.com - Google Play lists Onoff Numbers as an Onoff Telecom app with in app purchases, broad consumer distribution, virtual number features, and paid number or calling plan subscriptions.
- arcep.fr - ARCEP published a decision renewing mobile numbering resources for a company named Onoff telecom, supporting numbering regulation as material public context.
- RIPE registry record - RIPE NCC lists ONOFF TELECOM SAS as a member in France with address details and service areas, supporting the company's public network-operator context.
- annuaire-entreprises.data.gouv.fr - The French government company directory lists ONOFF TELECOM, SIREN 832 235 253, as an active SAS in other telecommunications activities, created on 13 September 2017, with 20 to 49 employees in 2023.
- docs.onoffbusiness.com - Onoff Business API documentation describes a REST API in beta for member management, number management, and department management, with availability described as limited to the Max plan.
Domain of operation
The ‘Technical Director’ label in public internet registry records is a RIPE role contact (TD7104-RIPE), not a verified individual. It is tied to ONOFF TELECOM SAS, a Paris‑based cloud telecom operator that provides virtual phone numbers under the Onoff brand. The profile surfaces the real entity behind the label to prevent misattribution of operational control.
- Registry RDAP / WHOIS record: public-source identity and registry context for Technical Director. Evidence basis: source-8e1f9127ebc9
Timeline
- Technical Director public evidence observed
The profile matters because it identifies the actual operating entity—ONOFF TELECOM SAS—a licensed telecom operator offering cloud‑based virtual numbers. Mistaking the role for a person misdirects attention from the company’s control over number assignment, service stability, and API reliability, which are the real dependencies for users and businesses.
At A Glance
- Name: Technical Director
- Type: Individual registry-holder label
- Base: France
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- documented relationships updates
Why It Matters
- Users and businesses depend on ONOFF’s ability to assign numbers, keep calls reachable, suspend accounts, and expose business APIs. Disruption or misuse of these controls can interrupt communications and business operations. Treating the registry role as a person instead of a company contact obscures where accountability sits.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- official company sources
- public registries
- operator-published records
Track verified source updates, role changes, and current public evidence.
Users and businesses depend on ONOFF’s ability to assign numbers, keep calls reachable, suspend accounts, and expose business APIs. Disruption or misuse of these controls can interrupt communications and business operations. Treating the registry role as a person instead of a company contact obscures where accountability sits.
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
Users and businesses depend on ONOFF’s ability to assign numbers, keep calls reachable, suspend accounts, and expose business APIs. Disruption or misuse of these controls can interrupt communications and business operations. Treating the registry role as a person instead of a company contact obscures where accountability sits.
Watchpoints
- ONOFF TELECOM SAS is a small but licensed European virtual‑number operator with a consumer and business split.
- Its strategic significance lies in the growing dependence on app‑based identity and communications, not in raw network infrastructure scale.
- The absence of BGP announcements under AS211948 means its footprint is currently voice/SMS‑centric, but any move into IP transit or peering would change its infrastructure profile.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track Technical Director?
The profile matters because it identifies the actual operating entity—ONOFF TELECOM SAS—a licensed telecom operator offering cloud‑based virtual numbers. Mistaking the role for a person misdirects attention from the company’s control over number assignment, service stability, and API reliability, which are the real dependencies for users and businesses.
What evidence supports the profile?
public-source identity and registry context for Technical Director.
What should readers watch next?
ONOFF TELECOM SAS is a small but licensed European virtual‑number operator with a consumer and business split.

