Summary

  • The record for Sunsern Sukwanichpaiboon states that the individual is listed in registry records with administrative and technical responsibilities, and attaches seven autonomous system numbers with Thailand as their region.
  • The seven registry pages cited as that record's basis resolved to no readable record on 18 October 2026, and no transfer instrument, appointment record or registry modification history naming the individual was obtained. A contact field identifies who is notified; it does not identify who may authorise a change.

What the record states, and what it does not

The record is a person entry: legal type person, headquarters country Thailand, registration jurisdiction Thailand, status published, with a stated confidence of 0.95 and a creation and last-update date of 17 June 2026. Its substantive claim is a role line — that the individual is listed in registry records with administrative and technical responsibilities — and its substantive attachment is a set of seven autonomous system numbers — AS45764, AS45788, AS45796, AS132821, AS134402, AS135670 and AS137885 — each with region TH, country Thailand, service ISP, and the person's own entry as owner reference.

Two features of that record deserve to be read literally rather than generously. The contact facet is marked gated, scoped to Thailand and to managed network and ISP service, and both its organisation name and its organisation slug are the person's own name rather than a separate company, ministry, university or foundation. And the record carries its own data gap: verify the current title, the organisational affiliation, the country context and the relationship to infrastructure events. A record that asks for its own role to be verified is telling the reader which part of it is settled and which part is not.

Seven pages that returned no record

The record's evidence basis points at registry pages for the seven numbers. On 18 October 2026 those pages were addressed and did not resolve to readable text: each returned an access failure with no quoted excerpt. The numbers themselves were therefore never read at document level — no registered holder name, no administrative or technical contact field, no registration date, no modification history. The seven pages remain the right destination for anyone who wants to check; what can be stated here is that they were not readable on that date, not what they say.

That distinction is the whole of the evidentiary problem. A directory that attaches network objects to a named person may be reading a holder field, a contact field, an abuse field or a routing field, and each of those means something different about authority. Without the page text, the attachment is an observation about a record, not a finding about a network.

A name with no other documentary footprint

An exact-name search of the public web on 18 October 2026 returned no public documents, articles or indexed entries carrying the name. That is a reported absence in one search on one date, and it should be weighted as such: a single search cannot establish that no filing, gazette notice or corporate registration anywhere names this person. But it does mean the review cannot place the individual in any second document — no appointment notice, no board or secretariat record, no counterparty filing, no conference programme — that would independently corroborate the role line.

The instrument classes that would settle it

The question the record cannot answer is an instrument question, and the candidate instruments are not interchangeable. A ministry approval authorises a body to act. A Royal Gazette publication gives an official act its public date and text. A foundation charter creates an organisation and defines its objects. A memorandum of understanding records an intention between parties, often without transferring anything. A transfer of registry membership moves an existing registration from one holder to another.

Those are five different documents with five different legal effects, and only some of them can move a registration. A charter that creates an organisation is not an assignment of existing registrations; an intention recorded in a memorandum is not a transfer; a gazette notice that announces a decision is not the same text as the decision. This is why the absence matters more than it first appears.

The instrument that would give a named contact the power to authorise a change to a network object sits in a corporate or regulatory record that is almost never read beside the registry entry — and until one of those documents is produced, the contact field has no counterpart.

The national layer does not close the gap. The Thai Network Information Center Foundation is described, in the summary obtained of its own site on 18 October 2026, as the registry for the .th country-code domain, with academic and research-network origins; the same summary states that a specific transfer instrument — a Royal Gazette publication or a ministerial approval — is not publicly detailed in the material available. That is a summary of a page, not the text of an instrument, and it is reported here in exactly those terms.

Falsification conditions, named in advance

Three findings would convert a contact field into a documented role, and they are worth stating before they arrive rather than after. First, a transfer instrument that names the individual as the responsible officer for the affected registrations. Second, a dated appointment, board or secretariat record placing them in the office whose duties include those registrations. Third, a registry modification history showing the same contact identifier surviving an organisational change — which would show a person carried across rather than a role reassigned.

None of the three was obtained. Until one is, the honest statement is narrow: the record establishes that a listing exists, that it carries role language, and that it is scoped to Thailand and to ISP service. It establishes nothing about who may approve a transfer, a revocation or a re-pricing.

Why the gap has consequences

Operators, counterparties and applicants read a named administrative and technical contact as the person who can authorise a change to a network object. That reading is usually good enough, which is precisely why the underlying instrument is rarely examined. It stops being good enough in a dispute. Where responsibility for a national resource is attributed to a contact field, a later argument about who may transfer, revoke or re-price it has no named counterparty to answer, and the document that would identify one tends to surface after the argument has already hardened.

The consequence is not that this individual lacks authority. It is that the record does not demonstrate authority either way, and the record is what most readers will encounter. A directory entry that renders a person from a contact field performs a small act of promotion; the correction is not to accuse the person of holding a role they may well hold, but to keep the two questions separate — who is listed, and what instrument put them there.

What would change this account

Any readable registry record for the seven numbers, any instrument text naming an office or a person, or any modification history would change this account, and would change it quickly. The absence described here is scoped to material actually read on 18 October 2026 and to the document classes named above. It is a statement about a record set, not about a life.