DNF SLD Checker Update on SLD Checker

[HelmutsHelmuts is verified member.]

Hello everyone,

SLD Checker has now been updated from v0.6-beta to v0.7-beta.

With this update, SLD Checker can now be discovered and used directly by compatible AI agents.

I have added instructions that compatible AI agents can read and understand on their own. This means an AI agent can now find SLD Checker, search domain names across supported extensions and work with the results without needing to open the website or fill in any search form.

I tested this from fresh AI agent sessions with no previous SLD Checker context and the agents were able to discover and use it successfully.

The normal SLD Checker interface remains unchanged for regular users:

SLD Checker

DNForum SLD Checker checks an exact second-level name across TLD extensions and shows total matches with Active, Parked, and Inactive status.

www.dnforum.com

This is an initial release so I will keep testing across different AI agents and improve it where needed. Feel free to share any feedback!

super!! Thank you for an update .. checking it now with Hermes agent + laguna s2.1:

 

[HelmutsHelmuts is verified member.]

hmm.. Laguna results are as follows (coy/paste below):

===

Here's the complete comparison formatted in BBCode:

────────────────────────────────────

DNForum SLD Checker vs dotDB: Agent-Friendly Comparison Test

Test: 10 random domain names × 2 tools, focused on agent usability and result quality

---

1. AGENT ACCESSIBILITY ASSESSMENT

DNForum SLD Checker — PASS

• Endpoint:

  GET https://sld.dnforum.com/api/v1/machine/search?keyword=KEYWORD&live=0

• Authentication: None required — no API key, no CAPTCHA, no cookies
• Response: Clean JSON with summary (total/active/parked/inactive) + results array
• Docs: Dedicated skill.md for AI agents + MCP server
• Rate limits: None — 10 queries in ~6 seconds
• Workflow: Single requests.get() → parse JSON → done

dotDB — FAIL

• Endpoint:

  GET https://api.dotdb.com/v2/search?keyword=KEYWORD

• Authentication: Requires paid Expert plan ($42.99+); returns 403 without API key
• Web scraping (HTTP): Cloudflare bot detection returns placeholder data after 3-4 requests
• Web scraping (Browser): Cloudflare interstitial ("Just a moment...") needs 8-10s manual wait
• Results format: AJAX-loaded HTML tables with tab-delimited tbody text
• Docs: No AI/agent integration documented
• Workflow: Headless browser → wait for Cloudflare → navigate → wait for AJAX → parse tbody

---

2. COUNT COMPARISON (10 KEYWORDS)

Keywords: solpaxu, grazaox, pulse, rexdroar, tordroor, sylquo, sigma, sunvexox, delta, raven

Keyword	DNForum Total	DNForum Active	DNForum Parked	DNForum Inactive	dotDB Total	dotDB Active
solpaxu	0	0	0	0	0	0
grazaox	0	0	0	0	0
pulse	289	106	23	160	527	396
rexdroar	0	0	0	0	0
tordroor	0	0	0	0	0
sylquo	1	1	0	0	2	2
sigma	267	80	29	158	498	371
sunvexox	0	0	0	0	0
delta	273	80	30	163	539	416
raven	233	87	10	136	361	267
TOTAL	1063	354	92	617	1927	1452

Key observations:

• dotDB higher total on 5/10 keywords — DNForum higher on 0/10
• dotDB advantage: 864 more extensions (81.3% more)
• dotDB advantage (active): 1,098 more active domains (310.2% more)
• Both tools agree on 5/5 random strings (all returned 0)
• Example discrepancy: pulse.com.au — DNForum=miss, dotDB=hit
• DNForum finds some newer gTLDs dotDB misses (e.g., pulse.beer, pulse.store)

---

3. EXTENSION OVERLAP (4 keywords with data from both)

Keyword	DNForum Only	Both	dotDB Only	Overlap %
pulse	18	271	256	49.7%
sigma	19	248	250	48.0%
delta	7	266	273	48.7%
raven	7	226	135	61.4%
Combined	51	1,011	914	51.2%

• ~51% of extensions appear on both tools
• dotDB finds ~914 extensions DNForum misses (mostly ccTLDs like .ac, .ad, .ae, .ai.in)
• DNForum finds ~51 extensions dotDB misses (mostly newer gTLDs like pulse.beer, pulse.store, IDN domains)
• Both agree on common TLDs: .com, .net, .org, .co.uk, .de, .io

Note from prior DNForum comparison thread (Sep 15, 2026): dotDB has a daily search limit that returns dummy rows after exhaustion, and DNForum counts can
change between initial and repeat searches due to live background enrichment. Neither tool is a complete registration record — verify with registry RDAP/WHOIS for
critical decisions.

---

4. PERFORMANCE

Metric	DNForum SLD Checker	dotDB
10 queries time	~6 seconds	N/A (no API)
HTTP requests needed	10 simple GET calls	Blocked after 3-4 (Cloudflare)
Browser automation	Not required	Required (8-10s Cloudflare wait)
Response format	JSON (structured)	HTML table + AJAX tbody

---

5. CONCLUSION

For AI agents: DNForum's SLD Checker is dramatically more convenient. A single

requests.get()

returns structured
JSON — no auth, no bot protection, no browser automation. It includes a documented skill.md for AI agents and MCP support.

For dotDB: Not viable for autonomous agents without a paid plan. The API is behind a $42.99+ paywall, and the free web interface is
blocked by Cloudflare bot detection. Browser automation works but is slow and fragile (interstitial challenges, AJAX-loaded content, placeholder data under rate
limits).

For result quality: dotDB finds ~81% more extensions (1,927 vs 1,063), primarily from broader ccTLD coverage. Both tools have ~51% extension overlap. Use
both as complementary research tools — neither is complete on its own.

Test conducted with Hermes Agent on September 22, 2026. Full report: MD report | Data:
JSON results

============

now, here is my manual bulk search for the keywords - I'm curious to see if there are discrepencies:

 

[HelmutsHelmuts is verified member.]

@birajst nice!! the agent access is spot on!! though, the original task - wuhhhh!!! please look more into this - laguna did use a new set of keywords > and, we are properly behind the dobd

.. we need to see why and where they kick our ass on providing more results on these