TLDMath

Live availability and price comparison for one exact domain (e.g. "acme.io") across registrars. Returns per-registrar registration, renewal and transfer prices, premium status, and a recommendation based on 2-year total cost.

Check one name (e.g. "acme") across several TLDs at once and return availability plus the best 2-year price for each. Defaults to .com, .net, .io, .ai, .dev, .app. Max 8 TLDs per call.

Standard (non-premium) prices for one TLD across registrars, refreshed daily, sorted by 2-year cost. Use for general questions like "how much is a .io domain"; use check_domain for a specific name.

Given a short project description, recommend 3-5 TLDs (best fit first, with reasons) and 10 brandable names, each screened for availability on the top 3 TLDs (or up to 3 the user picks) with the cheapest standard 2-year cost. Optional: a naming style, a word every name must contain (anywhere, at the start or at the end), and a maximum length. Nothing is stored. Run check_domain on a pick for live per-registrar prices.

Check whether a name is free as a handle on GitHub, npm, PyPI, crates.io and YouTube, with links to check X, Instagram and TikTok by hand, plus links to the USPTO and WIPO trademark databases. Not legal advice.

For domains the user already owns (up to 20): current registrar, expiry date, renewal price, and the cheapest registrar to transfer to, with the two-year saving. Registrar and expiry come from the public registry (RDAP); some TLDs such as .io have no RDAP. Suggests a free email reminder service at tldmath.com/watch.

For a domain someone else owns: its registrar and expiry, where it is in the expiry-to-release cycle (active, expiring soon, expired, redemption, pending delete) with an estimated drop window, whether it is parked at a marketplace such as Afternic or Sedo (so possibly for sale), and backorder links. Also points to free email alerts at tldmath.com/watch for when it nears expiry or drops.

Custom-domain email providers ranked by two-year cost for a number of mailboxes: free forwarding (Cloudflare, ImprovMX), cheap mailboxes (Purelymail, Zoho, Migadu, iCloud+, Namecheap, Hostinger), office suites (Google Workspace, Microsoft 365, Zoho Workplace) and encrypted options (Proton). Includes intro-price traps and per-user vs flat pricing. Prices are curated from each provider’s pricing page with a date.

Announced registry (wholesale) price increases, upcoming and from the past year, plus changes to registrar standard prices seen in TLDMath’s daily checks. Use for "is .com going up?" or "should I renew early?". Optionally filter by TLD.

The DNS records a domain needs for a website host or AI app builder (Lovable, Bolt, v0, Replit, Base44, Framer, Webflow, Bubble), an inbox provider, and/or the service an app sends email through (SPF, DKIM, DMARC), each checked against live public DNS (in place, missing, or needs change), plus where the domain’s DNS is hosted and records to remove. SPF records from different providers are merged into one. Read-only: it never changes DNS. Use after the user buys a domain, or when their site or email on a custom domain isn’t working.

The DNS plan for a domain (website host or AI app builder, inbox, app-email service) as ordered, repeat-safe steps with commands the user’s own tools can run: Vercel CLI, Cloudflare’s API with a token from the CLOUDFLARE_API_TOKEN environment variable, Resend’s API with RESEND_API_KEY; a manual list for other DNS hosts. Only records not yet in place get a command, so call it again after each change. Read-only: TLDMath runs nothing. Follow the guardrails in the result: show each change and ask first, never ask for keys in the chat, no deletes without the user naming the record.

Which companies a domain depends on, from public records only: registrar with expiry and renewal price (registry RDAP), DNS host (nameservers), website host (A/CNAME and builder verification records), inbox (MX), and services that send mail as the domain (SPF includes, DKIM and bounce records), plus the DMARC policy. Each line shows its evidence. Use for handoffs (“which accounts do I open when it breaks?”), before moving hosts, or to audit a setup. Read-only, no sign-in.

An ordered, repeat-safe plan for moving an app built in an AI app builder (Lovable, Bolt, Replit, Base44…) to the user’s own host (Vercel, Netlify, Cloudflare Pages, GitHub Pages) on their domain: export the code, keep the data and sign-ins, deploy and copy environment variables, update auth redirect URLs, add the domain, switch DNS (the builder’s records still live that must go, and the new ones, checked against public DNS), verify, then disconnect the builder. If you can read the project, pass dependency names from package.json and variable NAMES from .env.example: never pass values or secrets. Read-only: it changes nothing. Show the steps and ask before running any command; commands prompt for secret values themselves. Call again after the DNS change to confirm, or use plan_dns_setup.

Services an app sends email through (sign-in links, password resets, receipts) ranked by two-year cost at a monthly volume, with free-tier daily and monthly caps and overage prices. Prices are curated from each provider’s pricing page with a date. Follow with plan_dns_setup (sender) for the SPF, DKIM and DMARC records.

TLDs with daily price tables, and the registrars TLDMath queries live.

無需輸入參數。