#goy-spa{display:none!important} PRIVEX We run on it. Private servers, lax abuse policy. 5% off your first bill, code goymail Save 5%

GoyDNS

GoyDNS

Abuse

This notice concerns informal complaints addressed to the Operator in respect of domain names whose name servers are pointed at GoyDNS. Competence over lock and cancellation resides with the registrar of record and with the registry. We do not care.

NOTHING TLD;R

ConcernNothingsampled continuously

DeskTLD;Rregistry / registrar

DutyZerono ticket number

1. Situation

This page is the notice published at /abuse. The reader who has opened it has already treated the Operator as an addressee of a complaint concerning a domain name, or concerning conduct associated with a domain name whose name servers are pointed at GoyDNS. The address bar records that fact. What follows is the entire procedure afforded to Informal Communication. No ticket number is issued. No queue is opened.

A complaint of this kind ordinarily arrives because NS for the name is visible in RDAP or WHOIS, and because RFC 2142 has instructed a generation of offices that a mailbox of the form abuse@domain is where such mail belongs. Visibility of a nameserver identifies a locus of publication. It does not identify a party who can suspend, cancel, lock, or transfer the name. Those acts operate on the registry object. The registry object is created by the registry that runs the TLD and is sponsored, billed, and locked by the registrar of record. The remainder of this notice is an argument for that allocation of power.

Background. The reader is already on this page. The URL performs no clerical function. Nothing in this notice creates a duty to monitor, to respond, to investigate, to mediate, or to preserve. The Operator records that the reader has been shown the procedure, which is the text below.

2. On the Name

Before any office can be competent, the thing complained of must be identified. Ordinary speech treats "a domain" as one object with one owner and one remedy. The system that exists is otherwise. A name is several objects, loosely coupled by convention, and the powers that attach to each object do not travel with the others.

First, a name is a string in a namespace, allocated under a TLD. That string is a registry object. It is created in a database maintained by the registry. Statuses such as clientHold, serverHold, pending delete, and the various locks are attributes of that object. Cancellation, transfer, and renewal act on it. ICANN's Registrar Accreditation Agreement and the several Registry Agreements assign investigation and mitigation of DNS Abuse, as those instruments define the term, to registrars and to registries. The Operator is neither a registrar of record nor a registry operator.

Second, a name may be pointed at name servers. Pointing is a later act. It may never occur. When it does occur, the NS set published at the parent identifies hosts that will answer questions about the name. An authoritative nameserver, including those operated here, answers for zones an account has pointed here and refuses the rest. Glue, where glue exists, is an address published so that the NS host can be found. Glue is an addressing convenience. Title to the name remains with the registry object and with the sponsorship that the registrar of record continues to hold.

Third, a name may be used as a label for a website, a mailbox, a certificate, or a piece of speech. Those uses live on machines and in protocols other than the authoritative zone. A landing page is served by a host. Mail is accepted by an MX. A certificate is issued by a CA. Each of those operators has its own object and its own powers. Confusion among the three layers is the usual source of mail to this URL. The claimant has seen NS and has written as if a nameserver were a court of first instance over the registration. The Operator is a nameserver. It answers hosted names.

The error is a confusion of identity. The sign by which a thing is found is taken for the thing that can be acted upon. The sign here is NS. If the demand is takedown of the name, the proper object is the registry record. If the demand is removal of content, the proper object is the host. If the demand is a change of billing or of lock, the proper object is the registrar's sponsorship. The Operator holds answers. Answers do not unsell a registration, do not lock a TLD, and do not take down a page.

3. Competence

Competence is the power to perform the demanded act upon the proper object. A party may be morally moved, professionally instructed, and sincerely convinced, and still lack competence. Ought, in the sense that would bind a respondent, presupposes can. Where the object lies outside the subject's control, the purported obligation is empty: it commands an act that the subject cannot perform.

The Operator's competence is the publication of DNS answers for hosted names, paid in cryptocurrency, under a token shown once, subject to plan caps, as set out in the Terms. That competence does not include unselling a registration, placing a registry lock, issuing a UDRP decision, or adjudicating a mark.

RDAP, under the profile ICANN requires of gTLD registries and registrars, returns the sponsoring registrar, the registry, the NS set, and an abuse contact nested under the registrar entity. The abuse contact is there because the registrar is the office that sold the name and retains the contractual lever. Correspondence about the name belongs, in the first instance, with that office, and in the second with the registry that continues to hold the TLD even when NS points here. TLD;R names the order: the TLD, then the registrar.

A nameserver can stop answering for a zone it hosts. That act, if it ever occurs, is an exercise of the Operator's control of the box. It is unpromised, unscheduled, and unavailable as a remedy. A claimant who wants a name unpublished as of right must obtain that result from the offices that can grant rights over the registry object. The Operator offers no such grant.

4. The claimant

The claimant is typically a person writing from an office: Trust and Safety, brand protection, outside counsel, a registrar's own abuse queue, a newsroom, a household, a research desk, correspondence shaped as ICANN compliance mail, a commercial rival. Those titles describe the reader. GoyDNS maintains no counterpart titles. There is no Trust and Safety function here, no jobs board, and no intake that converts a portal severity into a ticket.

Playbooks in those offices often treat a visible nameserver as a "responsible intermediary." An intermediary, in the sense that would matter to the demand, would stand between the registrant and the continued existence of the name, or between the speaker and the publication of the page. The Operator stands between a resolver and an answer. The continued existence of the name is a registry fact. The page is a hosting fact. A complaint addressed to the nameserver therefore asks a question of the wrong subject.

RFC 2142 explains why abuse@goydns.com is published. It supplies a mailbox convention so that a class of mail has a destination. A convention about addressing does not create a duty to lock a zone, to lecture a registrant, or to appear on a call. Brand disputes, if they are disputes about confusing similarity, concern registry objects and marks; UDRP, URS, and their cousins run through registrars and designated providers. A registrar who already holds the lock sometimes forwards a ticket because WHOIS displayed these name servers. Forwarding does not transfer the lock. A nameserver cannot reverse a sale it did not make.

Press inquiries may print that the operator declined. TLD;R. Consult RDAP. We do not care. Injury to a person, however serious, likewise leaves the registry object where it is; write to the registrar of record and to the registry, and if Binding Process exists, take it to Leo. Research notes sometimes request a response timeline. None is kept. The URL of this notice may be cited. Correspondence shaped as ICANN compliance mail assumes a human process behind NS. ICANN's own complaint routes for DNS Abuse run against registrars and registries under agreements those parties signed. The Operator signed neither. A competitor's PDF does not move a zone.

The offices differ in letterhead. They converge on a demand for investigation, mediation, takedown, a named respondent, and an audience. The mailbox competent for that demand was the registrar's before this page was opened.

5. Background

5.1

A Name is a registry object, created by a Registry, sold by a Registrar, and only afterwards pointed, if pointed, at nameservers. NS answers hosted names and refuses the rest. Pointing NS at the Operator leaves investigation, mediation, and takedown with the Registrar and the Registry. The Operator therefore declines to treat Informal Communication as a proceeding.

5.2 On duty

One may ask why a good, once named in a letter, should become the Operator's affair. The question is older than DNS. A duty, in the sense that would bind a respondent, is a relation among a subject, an object, and an act. The subject must be capable of the act. The object must be the thing upon which the act can be performed. The subject must have undertaken the relation, by promise, by office, or by the kind of control that the law treats as assuming a role. Absent those conditions, the sentence "you must" is a wish wearing the grammar of a command.

The naming of a good does not move an object. A letter that recites harm recites a reason the writer has for wanting an act. Gravity of reason does not enlarge power. Power follows the object, and the object of cancellation is the registry record. That object remains with the registry. The Operator has undertaken to publish answers for hosted names. That is the affair. Adjudication of the uses of those names was never undertaken.

Commands of the form "you shall lock," "you shall sinkhole," "you shall produce the registrant" arrive from outside the system: a brand letter, a PDF, a forum thread, a photograph of a lanyard, a portal severity. They presuppose a prior undertaking. Publication of NS is not that undertaking. If a name is ever unpublished here, the act will be an exercise of the Operator's own control of the box. It will be unpromised, unscheduled, and unavailable as a remedy to a claimant. The claimant who wants a remedy as of right must seek it where rights over the Name are actually held.

5.3

Nothing in this notice creates a duty to monitor, to respond, or to preserve. Use of the service is acceptance of the Terms. The reader is on a notice and is reading it.

6. Definitions

Operator: Means the person or persons who run these nameservers, doing business as GoyDNS.
Name: Means a registry object: a string in a TLD, sold, billed, and sometimes pointed.
Zone: Means the records published here for a Name that an account actually hosts.
Registrar: Means the registrar of record, the office that sold the Name and retains the lock.
Registry: Means the operator of the TLD, who retains the Name even when NS points here.
Informal Communication: Means mail, forms, screenshots, lanyards, press, forums, "please advise," this GET form, and knocking justified by RFC 2142.
Binding Process: Means process that binds in the Operator's jurisdiction. See Leo. Informal mail has no such effect.
Duty: Means, for present purposes, zero. The charts below record the same measure.

Capitalized terms not found in this list are used in their ordinary English sense. The list exists so that later sentences may be exact.

7. Demands

The typical packet of Informal Communication contains a screenshot of a landing page, a photograph of a lanyard, a thread, or a press inquiry styled as a takedown. It often invokes "the users." In that invocation the users function as a phrase. A phrase does not reverse a registry sale.

RFC 2142 recommends a mailbox so that a class of mail has a destination. The destination may be copied. abuse@goydns.com is that destination. Copying it does not staff an office. Publication of an address is not the assumption of a mandate.

The catalogue of demanded acts includes lock of the zone, sinkhole of the name, disclosure of the registrant, disclosure of the account token, a written timeline, a call, an NDA, a display of regret, a display of care, and a person who answers the telephone. The Operator publishes NS. The remainder of the catalogue stays with the claimant.

Silence is available and will be used. A deed performed in order to satisfy a cause that the Operator did not adopt will not be performed. The charts repeat the measure.

8. Measure

n = 0

Concern, treated as if it were a quantity, was plotted against years. The line remained on the axis. Obligation, treated as if it were a weight, weighed nothing. The figures are that sentence drawn.

Relative competence over a Name

GoyDNS0%we answer NS

Registrar48%they sold the name

Registry47%they run the TLD

You5%you still have WHOIS

Derived from the allocation of registry power.

Cares remaining (n) vs year

The series is identically zero.

Index of obligation, by actor

Us0%authoritative DNS

Registrar100%contract with the registrant

Registry100%the TLD is theirs

You100%your ticket, your clock

Index 100 records the actor who holds the paper. Index 0 records the Operator.

9. Location of the Name

The Name is located by RDAP or WHOIS. The output identifies the registrar of record and the registry of the TLD. Those offices hold locks. The Operator holds answers for names pointed here, and a refusal for names that are not.

RDAP / WHOIS

whois example.com
curl -sS https://rdap.org/domain/example.com

If the output names a registrar, correspondence belongs there. If it names a registry, correspondence belongs there also. If it names these name servers, the reader has found the box that answers and has found this notice. TLD;R. A TLD, then a registrar. The Operator: nothing.

Exhibit A. Informal cover. From: To: Operator. Re: ABUSE / example.com. Demand: takedown by Friday. Attachments: lanyard.jpg, landing.png, thread.pdf. Disposition: the fields below print a stamp.

10. Form

GET

Offices are accustomed to forms. A form is provided. Submission records the typing in the query string. No ticket is opened. The stamp reads TLD;R. Correspondence belongs with the registrar of record, who has held the lock throughout the time spent reading.

11. Mailbox

abuse@goydns.com is a string. Publication of the string is not a promise of a clerk. Binding paper, if the reader has any, is addressed on Leo. The Operator does not cooperate with law enforcement. There is no duty to. Query logs do not exist. Do not write in order to obtain them. Do not write in order to ask whether the Operator cares. We do not care.

12. Close

TLD;R

The Name has been distinguished from the zone, the zone from the page, and the page from the sale. A duty has been shown to require a subject, an object, and an undertaking. The Operator possesses answers. The registrar of record and the registry possess the Name. The reader who wanted a procedure has been given that argument.

TLD;R: RDAP or WHOIS. Write to the registrar that sold the Name. Write to the registry that runs the TLD. Binding process: Leo. abuse@goydns.com is a string. A TLD, then a registrar. The Operator: nothing. We do not care.

GoyDNS