Domain name maximum registration limit
``` This ensures users see the current limit (hardcoded to **3**) before attempting registration. ### WHOIS Server Constraints The platform includes a minimal WHOIS server implementation in [`whois_server/whois.py`](https://github.com/DigitalPlatDev/FreeDomain/blob/main/whois_server/whois.py) that handles domain queries. While the server itself does not enforce registration limits, it reflects the restricted domain universe. You can query domain availability programmatically: ```python import socket HOST = "localhost" # or the remote host running the WHOIS service PORT = 43 # WHOIS port used by the server def whois_query(domain: str) -> str: with socket.create_connection((HOST, PORT), timeout=5) as sock: sock.sendall(domain.encode("utf-8") + b"\r\n") response = sock.recv(4096) return response.decode("utf-8") print(whois_query("example.dpdns.org")) ``` ## DNS and Infrastructure Constraints ### No Native DNS Hosting A critical DigitalPlat FreeDomain limitation is the **absence of built-in DNS hosting**. According to [`documents/tutorial/getting-started/1.2-dns-hosting.md`](https://github.com/DigitalPlatDev/FreeDomain/blob/main/documents/tutorial/getting-started/1.2-dns-hosting.md) (line 18), users must configure their domains to use external DNS providers such as **Cloudflare**, **FreeDNS**, or similar services. While this imposes an additional configuration step, it ensures there are no hidden bandwidth or query limits imposed by DigitalPlat itself. ### Abuse Handling Limitations The platform handles abuse reports manually rather than through automated systems. As noted in [`README.md`](https://github.com/DigitalPlatDev/FreeDomain/blob/main/README.md), response times vary from **a few hours to several days** depending on report volume. This manual review process, while necessary for accuracy, represents a service limitation for users seeking immediate resolution of domain disputes or takedown requests. ## Summary - **3-domain maximum** per account enforced across all TLDs to prevent abuse - **Restricted to 4 extensions**: .DPDNS.ORG, .US.KG, .QZZ.IO, and .XX.KG - **No built-in DNS hosting**; requires external provider configuration - **Manual abuse review** with variable response times (hours to days) - **Hardcoded limits** visible in frontend templates (`max_reg` variable) ## Frequently Asked Questions ### How many free domains can I register with DigitalPlat FreeDomain? Each account is limited to **3 free domains** total across all available TLDs. This limit is hardcoded into the platform's frontend and backend systems to prevent mass registration abuse. Users requiring additional hostnames should configure subdomains through their external DNS provider rather than registering new domains. ### Can I request an increase to the 3-domain limit? No, the DigitalPlat team is **not currently reviewing requests** to raise individual account limits. According to the FAQ documentation, this policy exists due to high volumes of abuse attempts. The 3-domain cap applies universally to all users regardless of use case or account age. ### Which domain extensions are available for free? DigitalPlat FreeDomain offers only **four specific TLDs**: .DPDNS.ORG, .US.KG, .QZZ.IO, and .XX.KG. These extensions are managed or delegated specifically to the DigitalPlat project to enable zero-cost registration. The README indicates additional extensions may be added in the future, but no timeline is provided. ### Does DigitalPlat FreeDomain provide DNS hosting? No, the service **does not include DNS hosting**. Users must configure their registered domains to use external DNS providers such as Cloudflare, FreeDNS, or other third-party services. While this requires additional setup, it means there are no bandwidth or query limits imposed by DigitalPlat on DNS traffic.