Questions people actually ask

Yes. No card, no trial, no tier that quietly expires. A handful of short names are held back as premium, but everything else is free to claim.

The catch is not money, it is attention: you keep a subdomain by signing in. See renewals.

A hostname like yourname.ajaira.site and a real DNS manager for it — A, AAAA, CNAME, TXT, MX and NS records, with TTL control.

You do not get hosting. We do not store your files or run your site. You point the name wherever your thing already lives.

Wherever you point it — your VPS, GitHub Pages, Vercel, Netlify, a Blogger blog. Claiming a name creates no DNS records of its own; you add those.

Until you do, it lands on a holding page of ours, because a catch-all record answers for anything that has no record yet. The moment you add one, yours wins and ours is out of the picture.

5 subdomains per account, 10 DNS records per subdomain. Starting limits, set low while the project is small. They will go up.

No. The setup guides cover Blogger, GitHub Pages, Vercel, VPS and Google verification step by step, and three of them have a one-click button that adds the records for you.

Free subdomain services fill up with names claimed once and never used. A weekly sign-in costs an active person nothing and returns abandoned names to everyone else.

Sign in. That is the whole process — it renews every subdomain on your account for another 7 days. There is no button and nothing to pay.

We email you 7 days out, then 2 days before. If the term ends anyway, the subdomain is marked expired and its DNS records are removed, so the hostname stops resolving.

We still hold the name for another 7 days. Signing in during that window brings it back with a fresh term. After that it returns to the pool and anyone can claim it.

No. The subdomain comes back, the records do not — they were deleted when it expired. You add them again. Keep a note of anything complicated.

Yes, in account settings. Your subdomains still expire on schedule — you will just not be warned.

Almost always caching, not a broken record. Check what the world actually sees:

dig +short yourname.ajaira.site
dig +short yourname.ajaira.site @1.1.1.1

If those show the new value and your browser does not, wait out the TTL you set.

A CNAME says “everything about this name lives over there instead”, so it would swallow your TXT verification and MX records too. The DNS spec forbids it and our manager rejects it before you can make the mistake. Use A or AAAA on @.

Longer version in A record vs CNAME.

We do. ajaira.site is delegated to our own nameservers, so a record you save is answered by us directly — no third-party DNS provider sits in between, and there is no per-zone record cap to run into.

Yes. Add NS records on your subdomain and it is handed to whichever nameservers you name — your own Cloudflare account, another provider, or a server you run. From then on you manage it there. Here is how.

No. One claimed subdomain becoming an unlimited supply of hostnames is too useful to whoever wants to abuse it. You can create normal sub-labels though — www.yourname.ajaira.site is fine.

Not yet. A, AAAA, CNAME, TXT and MX today. If you need one of the others, tell us what you are building.

Not from us — we do not host your site. Whoever does will issue one: GitHub Pages, Vercel and Netlify do it automatically, and on your own server Let's Encrypt works normally once the record resolves.

One of four reasons, and the checker tells you which: someone claimed it, it is reserved for infrastructure (www, mail, cpanel…), it is held back as premium, or it breaks the format rules.

3–30 characters, lowercase letters, numbers and hyphens. No leading or trailing hyphen, no double hyphen, and at least one letter.

Not self-service yet. Ask and we will tell you whether it is available and on what terms.

Not directly. Release it and have them claim it — but anyone can take it in between, so coordinate. If it matters, open a ticket and we will help.

Only if nobody else claimed it first. Releasing is immediate and permanent from our side.

Yes, when they are enabled — the buttons appear on the sign-in page. You can also link them to an existing account from settings.

We only accept an email address the provider has verified, because otherwise someone could claim your account by signing up elsewhere with your address.

Yes, from account settings. We will not let you unlink your last sign-in method until you have another one.

Yes. We send a confirmation link to the new address and a warning to the old one, so a stolen session cannot quietly move your account.

Account settings, at the bottom. It needs your password and a typed confirmation. Your subdomains and their DNS records go with it and the names return to the pool. There is no undo.

Yes — account settings has a JSON download with your account, subdomains, DNS records, tickets and activity log.

Phishing, malware, scams, spam, malicious redirects, impersonation and anything illegal. Those are suspended without warning. Full detail in the Acceptable Use Policy.

The abuse form. You get a reference and a link, and you can follow the thread and reply without an account. Phishing and malware reports open as urgent automatically.

Write to abuse@ajaira.site from the address on the account and explain. We do reverse decisions when we get them wrong.

No. We do not host it and we do not crawl it. We look when someone reports it.

An independent experiment, built and maintained with infrastructure from HostLagbe. It is not a HostLagbe product and is not trying to sell you hosting. See about.

Maybe, one day — it is a side project on sponsored infrastructure and we would rather say so than pretend otherwise. If we do, we will give notice on the site and by email. Do not put anything critical on a free subdomain, here or anywhere.

The free tier is the point. Premium names and larger limits may become paid later. We will announce changes before they take effect.

Claim something, build something odd, and post it in the group. If your company can provide infrastructure, see partners.