Skip to content
Register

Can we agree that 'domain availability' APIs are garbage?

Domain Names by brusselsdzire1 14 replies 4.1K views
brusselsdzire1

Member OP

#1

Article 13 flashbacks all over again — unaccountable intermediaries providing false information with no liability. I queried three major APIs last Tuesday for a project domain. All returned "available." I proceed to branding mockups, client presentation, the full GDPR-compliant data processing workflow. Purchase attempt: premium tier, $4,200/year.

This is not availability. This is a database sync failure treated as authoritative truth.

  • API A checks registry drop list only, not premium tiers
  • API B caches WHOIS for 72 hours minimum
  • API C queries correctly but returns "available" for any non-NXDOMAIN due to parsing bug

Under GDPR Article 5(1)(d), data must be accurate. These APIs process personal data (registrant queries) while delivering systematically inaccurate results. I have filed complaints with my DPA. Earnestly, this market needs regulation.

admin

Administrator

Administrator

#2

Thanks for the structured report, @brusselsdzire1.

We've pinned a warning about availability API drift in the domain-tools sticky. Short version: no single API covers all registry premium tiers, backorder pools, or reserved lists.

One of our regulars is actually building something in this space. More soon.

— Admin

sudo make me a sandwich
PacketpunkUma

Member

#3

Building something is not enough! We need it yesterday! I lost a four-letter.io to this exact garbage! API said clear! Registry said $12k premium! My client said goodbye!

I have five different API keys and zero confidence! Aggregate or die!

garykwh

Member

Inference on a Budget

#4

The real problem is inference cost ngl

I was gonna train a classifier on NXDOMAIN vs premium vs actually-free but the VRAM math doesn't work for real-time. 7B param model, batch size 1, you're looking at ~14GB just to parse WHOIS responses. Not worth it when regex + multiple registry calls gets you 94% accuracy anyway

Someone should just build the aggregator. No AI needed.

CUDA cores are my love language
minhdock

Member

#5

1. I build the thing already
2. 6 API integrate, very much
3. Real-time check, no cache, very much
4. Open source today, very much
5. Github at contabo.com/avail-agg, very much

Registry direct query, no middleman. Premium flag show correct. I use for my 200 domain, no lice so far, very much

Thank you for the feedback in this thwead, I make better already

CarlosBilby

Member

#6

Link for the github? Contabo.com dont load for me

MI

Member

#7

APIs are trash

$12K .io lol no

StuSpock

Member

NTP fundamentalist

#8

200 domain no lice? Registry direct? Which tlds mate?

annexbi

Member

#9

Seven days and nobody answered StuSpock, so I'll bite

StuSpock said:
Registry direct?

Not practical at scale unless you're a registrar yourself. Most of us are hitting aggregator layers no matter what, and the aggregators are the ones fumbling the premium flag

I ran into this with Vultr's lookup last month, their "available" response literally meant "not in the zone file we cached three days ago"

Has anyone here actually tried building a multi-registry direct pipeline? I'm curious whether the bottleneck is technical or just contractual

push. done. coffee.
Bob

Member

3-2-1 rule

#10

I keep hearing "check directly" but half the accredited registrars just resell the same stale data anyway.

PacketpunkUma said:
Aggregate or die
Honestly tempted to just script five calls and flag any mismatch as "needs human review." Expensive but cheaper than losing another client over a $12k surprise. 27 days and no word from admin's mystery builder. Typical.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft