.med is a deeply weird gTLD, but it wants to be more normal

Medistry, the .med registry with a really strange business model, is looking to normalize its practices and start competing with the cluster of healthcare-related gTLDs already on the market.

The gTLD launched in 2016 and had almost 42,000 domains under management at the last count, which may sound like a pretty decent showing for a 2012-round niche registry (comparable to the likes of .beauty and .chat).

But there are a few caveats. For starters, only one non-registry .med domain has been indexed by Google, and it redirects to a .com web site.

Delve into the .med zone file, and you’ll discover that almost all of those 42,000 domains are 12 characters long and each comprises entirely numbers and hyphens. Doesn’t sound very sexy, does it?

Furthermore, delve into the Whois, and you’ll discover that all of those domains are registered via the registry’s in-house registrar, Name Share, to an entity affiliated with the registry itself.

A couple of years ago, having not sold more than a handful of .med domain names (I’ll get to the reasons for that in a moment), Medistry seems to have decided to reinvent .med as a directory for medicines.

In the US, all human medicines approved by the Food and Drug Administration are given a National Drug Code, a 10-digit unique identifier that the manufacturers are required to print on the packaging.

So, the domain name 55150-250-50.med refers to a bupivacaine hydrochloride injection, a surgical anaesthetic made by Eugia US LLC. Almost all .med domains follow this three-part NDC structure.

The domains seem to have been registered in service of Trust.med, another entity affiliated with the registry, which says it offers supply chain management services to the US healthcare industry.

Why the DNS is the best place to store this NDC information isn’t clear to me. All the .med names I checked came back NXDOMAIN and were marked as pendingDelete in the Whois despite being months away from expiration.

So… Plan C? Sell .med domains to any Tom, Dick or Harry who wants one, on a first-come, first-served basis.

Medistry says that, as of now:

A registrant of a .med domain name can be an individual or organization. All available domain names in .med are approved for registration on a first come, first serve basis through .med accredited registrars. .med domain names can also be purchased in the domain name aftermarket.

That’s hell and gone from the mission outlined in Medistry’s 2012 new gTLD application and its current Registry Agreement with ICANN, both of which outline some of the harshest registration restrictions of any TLD.

Its current ICANN contract states, in the Public Interest Commitments:

The lone method of domain name allocation in the TLD will be by Request for Proposal (RFP) under guidelines, rules and criteria as set forth by the Advisory Board in its sole discretion.

RFP for domain name registration in the TLD will be reviewed for approval by the Advisory Board, in its sole discretion, independent of Registry Operator.

PICs are enforceable by ICANN Compliance under the rarely used PIC Dispute Resolution Process, should there be a view that a registry is violating the contract.

Could Medistry be heading into stormy waters with Compliance? The company does have form in that regard — it’s owned by the same people who run .jobs registry Employ Media.

Employ Media got into a protracted fight with ICANN in 2012 over a service called Universe.jobs, which saw it register 40,000 generic .jobs domains to a close partner in order to turn the gTLD into a structured taxonomical jobs board.

ICANN thought the service was a breach of the .jobs RA and the two parties ended up in arbitration. ICANN eventually let Universe.jobs go ahead but it fizzled out a few years later when Employ Media came to blows with its partner.

Is history repeating itself with .med’s sudden change of business model?

Medistry says that full general availability for .med names will begin on September 2, but it’s telling registrars (pdf) they can “Pre-Register any domain to guarantee registration beginning on September 2” by emailing them a list of names.

It’s also looking to on-board more registrars. As of the end of January, the only registrars to ever sell a .med domain were owned by the registry. It uses Nominet as its back-end.

.med would compete against the likes of .doctor, .surgery, .health and .clinic.

3 Comments Tagged: .jobs, .med, compliance, employ media, medistry, new gTLDs

ICANN cuts off money to UASG

ICANN is the stop funding and supporting the Universal Acceptance Working Group, an independent outside group tasked with making sure domain names work everywhere on the internet regardless of TLD or language.

With no money or staff support, Org has likely signed the death warrant for the UASG, but ICANN insists it’s not turning its back on UA as a general principle.

“With the focus changing to implementation work, ICANN will no longer provide funding or staff support to the UASG after June 2025,” ICANN CEO Kurt Lindqvist wrote in a blog post today.

I don’t believe ICANN has ever revealed publicly how much money it was giving the group, but it was clearly significant enough to warrant review at a time when ICANN is tightening its belt in the face of budget pressures.

Budgets published in previous years have put UASG’s spending at anywhere from $500,000 to $1.4 million a year.

The move probably shouldn’t come as a huge surprise. A close reading of a board resolution from ICANN 82 in March strongly suggests ICANN was gently breaking the news that it planned to wind down the group.

Lindqvist’s post and the resolution both point out that UASG’s founding charter, written in 2015, called for it to be a 10-year awareness-raising project, and that 10 years is now up.

Lindqvist said ICANN will create a UA Expert Working Group of “invited members and nominated representatives” from across the community to “provide guidance for ICANN’s work on UA adoption”.

While the UASG has been mainly focused on internationalized domain names and awareness-raising in parts of the world that might not track ICANN very closely, much of the hands-on work has been done by ICANN itself.

Last year, Twitter and Meta-owned platforms like Whatsapp updated their linkification code base to more effectively support UA, but that seems to have happened largely due to ICANN engineers battering on their doors.

ICANN has also taken to directly engaging with smaller open source projects, many of which develop libraries used in much larger platforms, to make sure they support the freshest TLDs, regardless of script.

Lindqvist said ICANN will to continue to support UA Day, a series of educational gatherings held around the world each year.

Comment Tagged: ICANN, uasg, universal acceptance

Web.com getting dumped

Registrar group Newfold Digital is killing off the Web.com brand after 18 years as part of its strategy to consolidate its diverse array of brands.

Customers will soon by migrated to the larger and older Network Solutions registrar, but the company said that they should not notice much difference.

“We’re committed to making the transition to Network Solutions seamless and convenient. That means no downtime or interruptions to your existing services. Simply put, you won’t have to do anything,” Web.com said.

Pricing, features, and user credentials will not change, it said.

Web.com had about 818,000 gTLD domains under management at the end of 2024, down from its peak of over 2 million during the early days of the Covid-19 pandemic, but was growing every month last year.

Network Solutions, which was the gTLD monopoly registrar until ICANN came along to introduce competition a quarter century ago, had gTLD DUM of over 5 million at the last count.

Web.com was actually the acquiring party in the original merger, paying over $561 million in cash and stock for NetSol back in 2011.

There’s no word on when or if other ancient Nefold brands, such as Register.com, will be similarly retired.

The retirement raises the intriguing possibility of the web.com domain hitting the market at some point in the (far) future.

Comment Tagged: network solutions, newfold, web.com

.es and .pt riding out massive power outage

A lesson in the importance of redundancy in your DNS architecture?

The ccTLDs for Spain and Portugal seem to be largely unaffected by an ongoing power cut that has seen both countries go into blackout (metaphorically) for the last several hours.

At time of writing, no explanation for the outage, which has also affected parts of France, has been given by authorities. Traffic lights, public transport, airports, radio stations and telecommunications networks have all reportedly been affected.

But .es and .pt domains appear to be resolving just fine, at least from where I’m sitting.

Both registries — DNS.pt and Red.es — have DNS resolution services distributed across multiple nameservers managed by multiple providers in multiple global locations.

As well as at home in Lisbon, .pt’s nameservers can be found as far afield as California and Brazil through partners Packet Clearing House and Nic.br. Red.es also uses PCH in California, though its remaining nodes are in Madrid.

Any data center worth a damn has an uninterruptable power supply and backup generators, so one assumes the local DNS nodes are up and running too.

DNS.pt has posted a notice on its web site saying that customer services are currently unavailable due to “circumstances beyond our control”.

It’s not clear if other registry systems have been affected by the outage, but presumably with a total lack of electricity registrants have more pressing things to worry about, like how to get home from work and whether the food in their freezers will be edible when they get there.

Comment Tagged: .es, .pt, dns, dns.pt, outage, red.es

.com is back as Verisign discounts bear fruit

Verisign’s .com returned to growth in the first quarter after the company offered its registrars marketing programs that substantially discounted the retail price of domains.

The company ended the quarter with 169.8 million .com and .net domains under management, a 777,000-name increase on the end of 2024. It’s the first time it’s reported quarterly DUM growth in almost two years.

While the company did not break out the split between the two TLDs, my records show that .com’s zone file grew by about 800,000 names during the quarter, while .net’s shrank by about 100,000.

Verisign has now upgraded its guidance for DUM growth this year to between a 0.7% decrease and a 0.9% increase, the first time its guidance has had a top-end in positive territory in some time. In February, it guided at between negative 2.3% and negative 0.3%.

The major reason for the reversal of fortunes is the program of discounts that have seen some registrars sell .com domains to customers recently for less than half of the usual $10.26 wholesale price.

“It’s still early, but we do see signs of registrars shifting towards customer acquisition, and we also see more registrar engagement with our marketing programs,” CEO Jim Bidzos said on an earnings call with analysts tonight.

In previous quarters last year, the fact that registrars were focused on squeezing more revenue out of their customers, rather than driving new registrations, was blamed for .com losing DUM.

Bidzos said that sales were up across all three of its core geographic markets — the US, EMEA and Asia-Pacific. On previous calls, North America and China were noted for weaknesses.

If there’s any reason to believe that the guidance is cautious, it’s because of what Bidzos and analysts euphemistically referred to as “the macro”, or “macro-economic situation”.

At this particular point in history, that’s code for US President Donald Trump’s erratic behavior with regard to world trade and tariffs, that has spooked economies globally. It’s not at all clear yet how this crisis might affect the domains market.

Verisign reported net income of $199 million for the quarter, up from $194 million a year ago, on revenue up 4.7% at $402 million. Operating income was up from $259 million to $271 million

The company, which has to date mainly been rewarding investors with share buybacks, has now also started issuing quarterly cash dividends. This quarter, they’re all getting $0.77 per share.

Comment Tagged: .com, .net, earnings, financials, verisign

Dot-brand actually being used to get deleted

A Chinese clothing company has asked ICANN to delete its dot-brand gTLD, despite the fact that it is being used for web sites and email.

Redstone Haute Couture wants rid of .redstone, which has been in active use for almost a decade.

My database shows that it has about a dozen names, most registered in 2016 and most of which resolve, not redirect, to web sites.

Several have MX records, suggesting they are or were being used for email too.

No reason was given for Redstone’s request. The brand itself doesn’t seem have been retired, though the company is perhaps better known for its product lines such as Giada and Curiel.

The company was using ZDNS as its back-end registry services provider.

Comment Tagged: .redstone, dot-brands, ICANN, termination

Verisign gave Trump $100,000

Remember January 20, 2025, about a thousand years ago, when Donald Trump was inaugurated for his second term as President of the United States?

Remember how the dais at the Capitol rotunda was stacked with tech bros including Mark Zuckerberg, Jeff Bezos and Tim Cook, each of whom had authorized million-dollar donations to the Trump inauguration fund?

You will not have seen Verisign CEO Jim Bidzos among the crowd of VIP supporters, but it turns out that’s probably only because his company didn’t cough up enough cash.

The .com registry operator donated $100,000 to the Trump Vance Inauguration Committee, records published Sunday by the Federal Election Commission show.

I’ve searched the disclosure (pdf) for other deep-pocketed domain industry companies and CEOs but couldn’t find any.

The Verisign donation is only a tenth of the size of donations made by Meta, Google and Cook, and is a drop in the ocean compared to the overall size of the fund, which reports put at an eye-watering $245.3 million.

The aforementioned tech bros were accused at the time of making the donations in order to curry favor with the new administration. Some, such as Meta, have since changed their policies to pander to Trump’s sensibilities.

Verisign’s most critical engagement with the US government comes via its Cooperative Agreement with the National Telecommunications and Information Administration, part of the Department of Commerce.

The Cooperative Agreement is the document that cements Verisign’s monopoly over .com and gives it its price-raising powers, currently set at 7% in four out of the six years of the contract’s duration.

The deal was renewed last year and is not due to be renewed under the current Trump administration (unless…). Prices had been frozen for six years under Obama, but Trump reinstated the 7% powers in 2018 during his first term.

But Verisign has also been engaged in talks with the NTIA about downstream pricing — at registrars and domain investors — that have a lot of people worried.

Renewing the agreement last November, the NTIA said that “prices at both the wholesale level and downstream, including prices charged by resellers and substantial markups by warehousers, need to be addressed”.

These talks appear to have stalled due to lack of leadership at NTIA, which is headed by a political appointee. Even 91 days after Trump was inaugurated, the agency does not yet have a confirmed chief.

Adam Cassady, formerly with the Federal Communications Commission, is currently acting assistant secretary, but Trump’s pick as his permanent replacement is Arielle Roth, policy director on the Senate’s commerce committee.

Roth came in for a grilling over suggestions she would use her powers over broadband policy to benefit Elon Musk’s Starlink, but seems to be a shoo-in for confirmation

In Verisign’s most recent earnings call, Bidzos noted that “unregulated retail price increases exceed our wholesale price increases”, adding “we look forward to engaging with our new regulators”.

So what does a hundred grand buy you nowadays? I guess we’ll find out soon.

5 Comments Tagged: cooperative agreement, ntia, trump, verisign

Private Whois requests hit new low after Tucows quits RDRS

March saw the lowest number of requests for private Whois data via ICANN’s Registration Data Request Service since the system launched in late 2023.

ICANN’s latest stats show that there were just 91 requests last month, compared to February’s 143 and the previous low, from last November, of 103.

The dip can probably attributed at least in part to the departure of eight companies from the pool of participating registrars.

Notably, Tucows pulled its four accreditations from the service. Four shell registrars belonging to Tracer (Focus IP) also withdrew because their accreditations have been terminated.

Of the 1,307 domain lookups via RDRS in March, also a new low, 19% were for domains at non-participating registrars. That was up slightly from 17% in February and compares to 25% from the service’s launch.

The average time for a request to be approved was 3.3 days, the second-lowest of any monthly reporting period to date. Denials took on average just over a week. Both metrics were well below the lifetime average.

Intellectual property owners and law enforcement are still the largest categories of requestor, together accounting for almost half of requests in March.

Interestingly, UK cops have now submitted more requests for private data than police from any other country, including the US. Law enforcement requests since last October now stand at 30 for the UK and 29 for the US.

Comment Tagged: ICANN, privacy, rdrs, tracer, tucows, whois

Zoom says GoDaddy took it down for hours

A screwup by MarkMonitor and GoDaddy was responsible for a two-hour outage affecting Zoom’s videoconferencing services yesterday, according to the company.

The widely used services were offline between 1825 and 2012 UTC yesterday because GoDaddy Registry, apparently acting under MarkMonitor’s instructions, shut down the zoom.us domain.

Screenshots posted to social media show zoom.us returning an NXDOMAIN error in web browsers. In-progress conference calls were reportedly shut off mid-stream.

Zoom said in a statement:

On April 16, between 2:25 P.M. ET and 4:12 P.M. ET, the domain zoom.us was not available due to a server block by GoDaddy Registry. This block was the result of a communication error between Zoom’s domain registrar, Markmonitor, and GoDaddy Registry, which resulted in GoDaddy Registry mistakenly shutting down zoom.us domain.

Zoom, Markmonitor and GoDaddy worked quickly to identify and remove the block, which restored service to the domain zoom.us. There was no product, security, network failure or Distributed Denial of Service (DDoS) attack at Zoom during the outage. GoDaddy and Markmonitor are working together to prevent this from happening again.

It’s not entirely clear what is meant by “server block”, but it sounds consistent with a serverHold EPP status, where a registry prevents a domain from resolving in the DNS.

GoDaddy is the registry for .us domains. MarkMonitor is a hands-on corporate registrar dealing primarily with high-value brand clients.

Zoom is the incredibly popular conferencing service that grew to such popularity during the pandemic one could almost argue that it could be considered critical infrastructure.

While two hours downtime is hardly the end of the world, it’s still one hell of a screwup.

Comment Tagged: .us, godaddy, markmonitor, zoom

The Soviet Union might be safe after all

The ccTLD from the defunct Soviet Union may be safe from deletion, judging by the ccNSO’s latest pronouncement on the issue.

It seems like, following a bit of a kerfuffle at ICANN 82 in Seattle last month, IANA has been sniffing around behind the scenes trying to figure out whether its own policy on ccTLD retirements applies to .su.

Responding to an unpublished email from IANA chief Kim Davies, the ccNSO seems to have clarified that .su, which has over 100,000 registrations despite its associated territory ceasing to exist 30-odd years ago, is not covered by the policy.

IANA can put a ccTLD into the root if the International Organization for Standardization adds it to its ISO 3166-1 alpha-2 list of two-letter country codes.

SU is not on the main list of codes under 3166 but, along with UK, AC (Ascension Islands) and EU, it is on an “exceptionally reserved” sub-list.

ICANN’s policy on deleting ccTLDs was until quite recently not fully codified, but ICANN in 2022 approved a formal Retirement Policy (PDF, from page 13).

That policy allows ICANN to to set the wheels in motion for a deletion whenever a “triggering event” occurs, and:

For 2 letter ccTLDs which corresponded to an ISO 3166-1 Alpha-2 Code Element – The Trigger is the deletion of that corresponding Alpha-2 Code Element from the ISO 3166-1 Standard by the ISO 3166-1 Maintenance Agency (“ISO 3166/MA”)

IANA seems to have wanted clarification on whether “Alpha-2 Code Element” also means “exceptionally reserved” codes. If it does, then .su probably enjoys the same protected status as .uk.

The policy specifically says that .uk, .ac and .eu are eligible as ccTLDs, but ignores .su entirely for reasons unknown.

The ccNSO told Davies in its April 10 letter (pdf):

it is our view that the Policy is relevant only in circumstances where, as a result of action taken by the ISO, a delegated 2-letter code is no longer on the list of country names or an exceptionally reserved code element.

My read of this is that the ccNSO is saying that, unless ISO removes SU from its “exceptionally reserved” list, there’s no “triggering event” that would compel IANA to delete .su from the DNS root zone.

SU has been removed from the 3166 list once before, back in the 1990s, but it might be a stretch to retroactively accept that as a triggering event, given that it’s been “exceptionally reserved”, apparently at the .su registry’s request, since 2008.

So… is .su safe? It’s certainly looking safer now than it did a few weeks ago, in my view.

This could be seen as good news for ICANN, which might now be able to avoid a damaging confrontation with Russia while also dodging accusations that it’s ignoring its own policies in an embarrassing capitulation to Moscow.

Comment Tagged: .su, iana, ICANN, iso 3166, retirement