Recommended Free Tools
A domain name is only the address: it does not run FoxyInvoice or create an email inbox. To put the project online, register the name, choose a host that supports the application, point its DNS records to that host, and configure email separately if needed. Those jobs can be handled by one company or several; the settings and responsibilities remain distinct.
What each service does
- Registrar: registers the domain name for a term and manages its renewal.
- Host: runs the website or application.
- Authoritative DNS provider: publishes the records that direct domain names to services.
- Email provider: handles mailboxes, forwarding, or application-generated mail.
A domain registration is not a deployment or a mailbox. For example, registering a name and then adding it to a hosting service requires both domain registration and the host’s custom-domain configuration. Cloudflare’s registration guide and GitHub Pages’ custom-domain guide document these as separate tasks.
As an Amazon Associate I earn from qualifying purchases.
How do I connect a domain to hosting?
- Secure the project accounts. Use accounts controlled by the project owner, with durable contact details and recovery options. Keep track of who controls registrar, hosting, and DNS access. Requirements vary by provider: for example, Cloudflare requires a verified account email for domain registration or transfer and collects registrant contact details.
- Register the domain. Choose the name and extension, check availability and renewal terms with the registrar, and provide accurate contact information. Registration secures the name for its term; it does not deploy FoxyInvoice. Cloudflare Registrar enables auto-renew by default, but its guidance still recommends checking that renewal succeeds; that default should not be assumed for other registrars. See Cloudflare’s registration guide and renewal guidance.
- Choose a compatible host. First establish FoxyInvoice’s actual runtime, database and storage needs, background jobs, and deployment workflow. Then select a host that supports those requirements. The available custom-domain instructions do not establish that FoxyInvoice can run on GitHub Pages or any other static-site host.
- Decide where DNS will be authoritative. The registrar and DNS provider do not have to be the same company. If you move DNS to Cloudflare, add the domain there, review or import its records, then update the nameservers at the registrar. Nameservers determine which provider is authoritative. Before switching, preserve records for the website, mail, verification, and other services: Cloudflare warns that missing or incorrect records can make the domain unreachable. Follow Cloudflare’s DNS setup instructions.
- Add the domain at the host and create its DNS records. Follow the chosen host’s current instructions for both its configuration and the DNS provider’s settings. The apex name (such as
example.com) andwww.example.comare distinct hostnames; configure each one you intend to use, or set up a redirect if appropriate. Record values vary by host, so do not copy an A or CNAME example from an unrelated service. Cloudflare’s domain onboarding guide and GitHub Pages’ guide explain the need to configure DNS alongside the host or repository. - Verify the connection. Confirm the registrar lists the domain as active, the host recognizes the custom domain and reports its HTTPS status, and DNS responses match the host’s required records. A host may require you to complete a domain-verification or HTTPS step in its dashboard as well as publish DNS records.
How do I set up email with my domain?
Choose the email function before changing DNS. Incoming forwarding, a mailbox that can send and receive, and mail sent by an application are different needs. Cloudflare Email Routing can forward incoming mail; sending and receiving requires an SMTP provider. The appropriate records depend on the provider, so use its current instructions rather than sample values from another service. See Cloudflare’s email-records guide.
Free tools Windows power users keep installed
One-click scans. No signup required.
Receiving and sending mail
MX records direct incoming mail to the mail provider. Providers may also require SPF and DKIM records for authentication, and a DMARC record to tell receiving systems how to handle messages that fail authentication and where to send aggregate reports. Cloudflare describes SPF as identifying authorized senders, DKIM as cryptographically authenticating the sender and message integrity, and DMARC as setting policy for SPF or DKIM failures. Start with the policy recommended by the chosen provider; do not move straight to a strict reject policy without accounting for every legitimate sender. See Cloudflare’s security-records documentation.
#1 Best Overall
- Brand New in box. The product ships with all relevant accessories
Avoid conflicting records
Do not create multiple SPF TXT records beginning with v=spf1; follow provider guidance to add authorized senders to the existing SPF policy. Cloudflare also documents that its Email Routing MX records and Google Workspace MX records cannot coexist on the same domain. If you change mail providers or routing, reconcile the MX records rather than leaving incompatible configurations in place. See Cloudflare’s Google Workspace DNS guide.
Understand the SPF lookup limit
Cloudflare’s 2026 guide explains that RFC 7208 limits a single SPF check to 10 DNS lookups; exceeding that limit can cause a permanent SPF error. This is a limit on lookups performed during SPF evaluation, not a cap on all DNS records or all DNS queries. See Cloudflare’s DNS lookup-limit guide.
What to check before and after switching providers
- Application compatibility: verify runtime, database, persistent storage, scheduled work, deployment workflow, and support for FoxyInvoice’s actual architecture before choosing a host.
- Portability: check whether you can move registrar, DNS, hosting, and mail independently, and whether any service requires its own nameservers. Cloudflare Registrar says domains registered through it cannot use another DNS provider’s nameservers while using that registrar.
- Account continuity: confirm contact and recovery details, renewal settings, payment method, and who retains ownership access. Renewal behavior is provider-specific.
- Mail compatibility: distinguish forwarding, full mailbox service, and application sending; check provider-specific MX, SPF, DKIM, and DMARC requirements against any existing routing setup.
- Current costs and availability: compare renewal rates, hosting limits, mailbox pricing, taxes, and geographic availability directly with providers. These details vary and are not established here.
How long do DNS changes take?
Allow time for DNS changes to appear across networks. Cloudflare Email Service says changes can take up to 24 hours globally and are usually visible within 5–15 minutes for domains using Cloudflare DNS. That is Cloudflare’s estimate for its service, not a universal guarantee. Check the host and email provider’s status or verification pages before treating a delay as a misconfiguration. See Cloudflare Email Service’s domain configuration guidance.
Who controls the domain, DNS, hosting, and mail?
Write down which account controls each role, even when one company supplies several of them. This makes renewals, record changes, recovery, and future migrations easier to manage. Keep a record of the DNS entries required by active services before changing nameservers or replacing a provider; the new authoritative DNS provider must publish the records those services need.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
