Summary

  • The handle 'novacloud-admin' corresponds to no registered role, person or mailbox object; the closest registry object is the maintainer novacloud-mnt attached to AS209874, and a maintainer is not an administrative contact.
  • Administrative authority under the NovaCloud-Hosting name is visible in named objects: role novacloud-hosting (NA8939-RIPE) as admin-c and tech-c of AS209874, abuse-c NA8940-RIPE, and organisation ORG-MWUL2-RIPE — Tech Tide Portugal Unipessoal LDA, reg-nr 517354420.
  • AS214789 belongs to a different operator entirely: Nova Cloud LLP (ORG-NC138-RIPE, Kazakhstan, reg-nr 240440015497), with an abuse mailbox on the novacloud.kz domain and no public document linking it to the Portuguese registrant.
  • The operator's own published contacts diverge from the registry: a NOC mailbox on as209874.net versus the registered abuse mailbox on novacloud-hosting.com for the same AS number.

An administrative handle is a claim about control. The interesting question is not whether the claim is literally true, but what the surrounding control surface reveals: which objects carry the authority to modify, who is obliged to answer for abuse, and where the operator's own presentation diverges from its registered duties. That question was left open by the earlier finding that the NovaCloud name is used by at least six unrelated entities across jurisdictions; this briefing maps the objects that actually hold the pen.

The handle that resolves to nothing

Querying registry material for the exact handle 'novacloud-admin' returns no role object, no person object and no mailbox. What does exist is maintainer novacloud-mnt, listed among the mnt-by references on AS209874 alongside RIPE-NCC-END-MNT and SBL-MNT (1, 2). The distinction matters operationally. A maintainer object guards which credentials may create or modify objects — it is an authorisation artefact; a role object describes the people performing a function and carries the contact obligation (3, 4). A brand-style maintainer label therefore proves authorisation over a resource, not administration of a network, and nothing in the public record binds the two strings together.

The directory entry itself carries the label COMPANY, but that is an editorial classification, not a registry fact; no registry object carries the handle the label names (5). Any reader who treats the handle as a corporate identity is borrowing an inference the evidence has not paid for.

What the numbered objects do show

The aut-num AS209874, registered as 'NovaCloud-Hosting Network', lists admin-c and tech-c NA8939-RIPE — the role object novacloud-hosting, with a NOC mailbox on the novacloud-hosting.com domain, created and last modified 2024-09-13 (6, 7). Its organisation object, ORG-MWUL2-RIPE, is Tech Tide Portugal Unipessoal LDA, country PT, reg-nr 517354420, with a sysadmin mailbox on the same domain as the contact and abuse-c NA8940-RIPE; the registered abuse contact for the AS resolves to the registered abuse mailbox on the novacloud-hosting.com domain (8, 9). The sponsoring organisation is ORG-SL1164-RIPE, and mirror timestamps show the aut-num last modified 2026-02-26 and the organisation 2026-05-13 (10).

Two inconsistencies sit inside this same record. First, the role object's address is in Faro while the organisation object's address is in Quarteira — a small mismatch, but exactly the kind of divergence that complicates serving legal notices. Second, the reported allocation date of 2025-04-24 conflicts with an earliest observed route origination of 2018-11-18 for the same number, which may indicate a previous holder (11, 12, 12a).

AS214789 shows what separation looks like in the same registry. Its as-name is nova-cloud-kz; the organisation is ORG-NC138-RIPE, Nova Cloud LLP, Kazakhstan, reg-nr 240440015497; admin-c and tech-c are MV16118-RIPE; the maintainer set is RIPE-NCC-END-MNT and kz-novacloud-mnt; and the registered abuse contact is a mailbox on the novacloud.kz domain, routed via abuse-c NA8821-RIPE. The aut-num was created 2024-05-31 and last modified 2024-07-02 (13, 14, 15, 15a). One of its prefixes reportedly uses a different abuse address, on an ip-rent.kz domain — a second divergence inside a single operator's footprint. No public document attributes both AS numbers to one beneficial owner, and none links the several same-named NovaCloud companies by ownership or control.

Where the operator's own record diverges

The operator's site presents AS209874 as 'NovaCloud-Hosting Network' delivering IP transit across Europe, with an operations mailbox on as209874.net (16). The registered abuse mailbox, however, lives on novacloud-hosting.com (17). Nothing prevents an operator from running multiple contact domains, but the pattern is instructive: the RDAP response for AS209874 presents an abuse-role entity with the fn 'novacloud-abuse', kind 'group' and an abuse-type email — precisely the structure RDAP standardises (18, 19, 20). Accountability is machine-readable because it is object-bound. A display handle like novacloud-admin, by contrast, appears in no object at all.

Vendor classification adds its own noise: IPinfo describes AS209874 as a hosting ASN with 1,206 hosted domains and 4,352 IPv4 addresses, while IPGeolocation.io labels it ISP (21, 22). Traffic estimators profile the novacloud-hosting.com domain without confirming ownership (23, 24). The registrant's imprint and service documentation describe Portuguese operations and customer requirements but do not establish the entity behind the Kazakh AS (25, 26).

What the object model obligates

The RIPE object model is explicit about where duty attaches. Role objects exist to describe a function performed by one or more people; mntner objects guard creation; abuse-c binds abuse handling to an organisation or role (27, 27a, 28, 29). RIPE-705 codifies the community's abuse-c reachability requirements, and the archived 2019-04 proposal record shows how those requirements were argued (30, 31). RPSL and its routing policy extension define the object grammar (32, 33). On the generic-registration side, the ICANN Registration Data Policy governs what contact data contracted parties must collect and publish, and ICANN maintains a compliance complaint channel where published obligations fail (34, 35). The live RIPE database query interface is the authoritative check against which mirror values should be re-verified (36).

The practical consequence: an operator can publish any display handle it likes, but its accountability perimeter is exactly the set of objects that carry mnt-by, admin-c, tech-c and abuse-c references. In the NovaCloud case that perimeter is legible and split — a Portuguese organisation with a Faro/Quarteira address mismatch on one AS, a Kazakh LLP with a divergent prefix-level abuse address on the other, and no documented bridge between them.

All registry object details in this briefing come from third-party mirrors and provider reads of public pages, not from independently opened live RDAP objects; values may lag the authoritative RIPE database. Abuse-handling performance and dispute records are absent for all operators.