Topic
DNS Delegation Power
Within the Topic facet, DNS Delegation Power topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
ICANN
The Takedown Notice Did Not Become a Verdict: Petroliam Nasional v. GoDaddy
The Ninth Circuit did not call every registrar passive or every takedown request futile. It drew a narrower, more useful line: a service provider's ability to maintain and forward a domain name does not create an unwritten ACPA claim that turns notice into adjudicatory authority.
IETF
How DNSSEC learned to prove a name does not exist
A signed answer can authenticate a record that is present. The harder design problem is authenticating the empty space where an attacker might otherwise hide a name, invent one or replace a truthful “no” with a forged response.
History
A Map Pin Was Not a Measurement
DNS LOC could express a coordinate to a thousandth of an arcsecond while declaring a horizontal error circle ten kilometres across. That was not a contradiction. The format distinguished the fineness of an address on a map from the strength of the knowledge behind it. A consumer…
ICANN
The Public Query Became a Private Lead Machine: Register.com v. Verio
A daily list of newly registered domains looked like public infrastructure until Verio connected it to automated WHOIS queries and rapid sales calls. The resulting case is less a monument to web-contract doctrine than a practical warning about layered permission: public data, a…
ICANN
When a DNS-Abuse Report Becomes Actionable—and What the Contract Still Does Not Order
The decisive step in ICANN's DNS-abuse regime is not the arrival of an allegation. It is the moment when available evidence supports a reasonable finding, after which a registrar or registry must act promptly—but still choose a remedy that fits its role, the harm and the risk to…
CASE FILE
The Certificates Did Not Expire: Chrome's Entrust Cutoff Turned Trust Into an Operating Licence
The decisive field was not the expiry date printed inside a TLS certificate. It was the timestamp proving when that certificate entered the public record—and whether Chrome still accepted the authority behind it at that moment.
History
The Hint That Had to Be Replaced by an Answer: DNS Root Priming
A recursive resolver begins with an awkward form of knowledge: enough addresses to reach the DNS root, but no current root data in its cache. Priming is the small exchange that turns that inherited hint into an authoritative, expiring answer.
IETF
The secret server name still needs a public front door: ECH’s new privacy boundary
Encrypted ClientHello gives a TLS connection two introductions: one the network may see, and one only the service can open. That is a real privacy gain, but it is not disappearance. The destination’s protection now depends on DNS configuration, a shared front door, key rotation…
ICANN
One Portal, No Clock: Who Actually Grants Zone-File Access?
CZDS lets a researcher ask many generic top-level-domain registries for zone files from one place. The common doorway is easy to mistake for a common decision. It is neither automatic access nor a single permission desk.
ICANN
The Forged Letter That Moved Sex.com: Kremen v. Cohen and Network Solutions
A forged instruction did not move a physical entity. It changed the authoritative registration record for a domain name—and forced a federal appellate court to ask what, exactly, the registrant controlled.
ICANN
A Domain Name in a Receiver’s Hands: Office Depot v Zuccarini
The judgment was entered in Florida, the debtor lived elsewhere, the registrars were scattered across three countries, and the `.com` registry sat in Northern California. To collect the debt, the Ninth Circuit had to decide where an intangible domain name could be found.
History
Two Queries, Two Servers: Why DNS Needed NSID
A service address can stay the same while the machine answering changes. DNS needed a way to identify the instance behind a particular reply, not merely whichever instance answered the next question. The resulting standard made the association precise while leaving the identity…
History
The Bit That Could Not Keep a Service Running: Why DNS WKS Never Became a Live Directory
Before opening a connection, an early Internet mailer could inspect one bit in DNS and decide whether a server existed. The bit was exact. The world behind it was not.
ICANN
The Four-Hour Transfer Contact That Cannot Reverse the Transfer
The Four-Hour Transfer Contact That Cannot Reverse the Transfer intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
ICANN
The Writ Reached ICANN; the Registry Data Stayed Abroad
The creditors proposed to sell or license operation of `.ir`. A court could reach ICANN in the United States, but an order changing the root-zone pointer would not deliver the foreign registry’s database, secure a competent successor or oblige the world’s networks to follow the…
ICANN
The drafting room behind root advice: who controls the RSSAC Caucus pipeline?
Most RSSAC reports are built in a body far larger than the committee that formally approves them. The current rules make that division visible: experts may propose, research and draft; root server operator representatives keep the gates for admission, scope, amendment and…
ICANN
The security advisers the Board appoints: where SSAC authority stops
Three dates describe the gate. On 25 November 2025, an internal membership committee recommended three candidates. On 10 December, SSAC approved them by consensus. On 25 January 2026, the ICANN Board appointed them. Expertise entered through a committee of incumbents and acquired…
CASE FILE
The 30 Percent Congress Legalised After It Was Collected
For two and a half years, every covered domain registration carried a public-purpose assessment that Congress had not specifically authorised. One month after a judge exposed the defect, Congress made the past lawful “as if” it had acted first.
History
The Name That Chose a Service: How DNS SRV Found Servers
A domain once led clients toward one address and a remembered port. DNS SRV made service location an explicit, bounded choice among hosts.
History
The Alias That Could Not Move Authority: DNS DNAME
DNAME redirects descendant lookups by replacing one suffix. The owner, zone apex and NS delegation stay put even when many queries follow the new subtree.