FreeDomain

DigitalPlatDev/FreeDomain

Free domain registration and practical DNS learning resources for everyone.

Ship status

Slowed

Last push 31–120 days ago. Quiet, not gone.

Last push
Aug 12, 2026
51 days ago
Ship score
33/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 194,174 → 201,546 (Aug 18 – Sep 29, 2026)
+4,641 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
202.2K
Forks
4.4K
Open issues
38
Watchers
292
Primary language
Markdown
Created
May 30, 2024
Owner
DigitalPlatDev · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 2 startups in the directory ship primarily in Markdown.

Topics

#digitalplat#dns#dns-tutorial#documentation#domain#domain-platform#domain-registration#domainname#domains#education#free#free-domain#freedomain#internet-infrastructure#nameserver

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose teaching material instead, and put os_startup at 46% (self-hostable 35%, hosted offering 34%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: slowed — last push 2026-08-12This is the badge for DigitalPlatDev/FreeDomain, as served from the URL below.
[![OSSEAN: slowed](https://ossean.com/badge/DigitalPlatDev/FreeDomain.svg)](https://ossean.com/DigitalPlatDev/FreeDomain)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.