Subdomain-as-a-Service
A real hostname for every project, with DNS you control.
Claim a subdomain, then manage A, AAAA, CNAME, TXT, MX, SRV and CAA records from the dashboard or the API.
Features
Infrastructure-grade DNS, sized for side projects
Multiple root domains
Claim names across every root domain the platform operates, each with its own rules.
Seven record types
A, AAAA, CNAME, TXT, MX, SRV and CAA with per-type validation before anything reaches DNS.
Namespace isolation
Every write is checked server-side against your hostname. Nobody can touch the parent zone or a neighbour.
Confirmed changes
Records show pending until the DNS provider confirms. Failures retry with backoff and surface clearly.
Scoped API keys
Per-key permissions, expiry and usage. Keys are hashed at rest and shown exactly once.
Audit trail
Every change is recorded with actor, request ID and before/after values.
How it works
From name to live record in four steps
- 01
Search a name
Type a label and see availability across every open root domain instantly.
- 02
Claim it
Sign up, verify your email, and the hostname is atomically reserved for your account.
- 03
Add records
Point it at your server, CDN or mail provider from the DNS editor or the API.
- 04
Go live
Changes are pushed to the authoritative DNS provider and tracked until confirmed.
DNS management
Your namespace, strictly bounded
You manage the hostname you claim and everything beneath it. The platform keeps the parent zone and every other customer out of reach.
When you claim john.orbinex.in, that hostname and everything below it — www.john.orbinex.in, _acme-challenge.john.orbinex.in — becomes your namespace.
Names are written relative to it: @ is the hostname itself, www is a child. Anything outside your namespace is rejected by the server, not just hidden in the UI.
Depending on the root domain, your records live in a shared, strictly bounded zone or in a dedicated zone delegated to you with NS records. Either way, provider credentials never leave the platform.
| Type | Name | Content |
|---|---|---|
| A | @ | 1.2.3.4 |
| CNAME | www | app.vercel-dns.com |
| MX | @ | 10 mail.example.com |
| TXT | _dmarc | v=DMARC1; p=none |
Developer API
Automate DNS from CI, scripts and agents
- Versioned REST API under /api/v1 with OpenAPI docs
- Bearer API keys with per-key scopes and expiry
- Async writes: 202 Accepted, poll until active
- Consistent error envelope with request IDs
curl -X POST "https://orbidns.example/api/v1/subdomains/{id}/records" \
-H "Authorization: Bearer $ORBIDNS_KEY" \
-H "Content-Type: application/json" \
-d '{"type":"A","name":"@","content":"1.2.3.4","ttl":300}'Pricing
Start free. Upgrade when you need more.
FAQ
Questions
- What exactly do I get?
- A hostname such as project.orbinex.in and full control over DNS records at and below that name, within your plan limits.
- Can I use it for email?
- Yes. Add MX records for your mail provider plus TXT records for SPF, DKIM and DMARC.
- Does it work with Vercel, Netlify or Cloudflare Pages?
- Yes. Add the CNAME (or A) record your host gives you, and any TXT verification record they ask for.
- How fast do changes apply?
- Changes are pushed to the DNS provider within seconds. A record turns active once the provider confirms; resolvers may cache old answers for up to the previous TTL.
- Can I get HTTPS certificates?
- Yes. Use HTTP validation, or DNS validation with a TXT record at _acme-challenge. CAA records let you restrict which CAs may issue.