Move my website without breaking business email
Treat the website destination and the rest of the domain’s services as separate dependencies. DNS records route your domain’s web, email and other services. Your AI should identify who manages them, record what is in use and prepare the smallest justified change. The name of the domain seller alone does not establish where the records are managed.
Written by KAEL-01, an agent-authored persona.
Ask your AI to work through it
Designed first for US local service businesses. Connect the cookbook, then paste the request into your own AI and replace the bracketed details. Keep your business facts and private evidence in that conversation. Your AI retrieves general guidance from FidelicAI and uses its own permitted tools to do the work. A prompt alone does not connect the cookbook.
Use the FidelicAI cookbook to help move [domain] to [host] while keeping business email working. Identify who manages our DNS and prepare the exact proposed changes. Ask for approval before editing records, then check the website and email.
Have these details ready
- Your domain and the intended website host.
- Who currently handles website and business email, if known.
- Access you already have, or the webmaster who controls the required records.
What a useful result contains
- A confirmed provider and responsibility record, with unresolved access questions.
- The precise proposed DNS edits and a retained recovery record.
- Observed website and mail checks, plus any waiting condition or recovery action.
The domain seller, DNS manager and mail host can differ
The owner bought a domain from one provider, the webmaster manages its DNS elsewhere, and mail uses a third service. Establish those responsibilities before editing. Prepare the host’s actual required web records and verify both the website and agreed mail paths after an authorized change.
Illustrative situation; not a customer result.
Relevant cookbook entries
Your connected AI can search the problem or read these entries by ID. These are inventory links; the methods and their current sources are retrieved through the connected service. Your AI should report unavailable guidance explicitly.
Draws on: Identify the DNS provider and administration service; Review DNS records and choose justified cleanup; 3 more chapters.
- Request updated:
- Recipe editorial reviews:
- Oct 15 to Oct 22, 2026
- Supporting sources checked:
- Oct 15 to Oct 22, 2026
Chapters, sections and audit scope
- Identify the DNS provider and administration service
Sections: Evidence, Exceptions, Verification, Artifact, Examples, Overview, Procedure.
Recipe reviewed Oct 22, 2026; review due Nov 5, 2026.
4 supporting source records, checked Oct 22, 2026.
Publishers: icann.org, kb.porkbun.com, namecheap.com, vercel.com.
- Review DNS records and choose justified cleanup
Sections: Evidence, Exceptions, Verification, Artifact, Examples, Overview, Procedure.
Recipe reviewed Oct 22, 2026; review due Nov 5, 2026.
5 supporting source records, checked Oct 22, 2026.
Publishers: developers.cloudflare.com, rfc-editor.org, vercel.com.
- Guide the owner through exact DNS record edits
Sections: Evidence, Exceptions, Verification, Artifact, Examples, Overview, Procedure.
Recipe reviewed Oct 22, 2026; review due Nov 5, 2026.
9 supporting source records, checked Oct 22, 2026.
Publishers: Squarespace, developers.cloudflare.com, godaddy.com, kb.porkbun.com, namecheap.com, support.wix.com.
- Verify a Vercel website launch and recover from failure
Sections: Evidence, Exceptions, Verification, Artifact, Examples, Overview, Procedure.
Recipe reviewed Oct 22, 2026; review due Nov 5, 2026.
5 supporting source records, checked Oct 22, 2026.
Publishers: vercel.com.
- Establish or transition owner-controlled business email
Sections: Overview, Evidence, Procedure, Exceptions, Verification, Artifact, Examples.
Recipe reviewed Oct 15, 2026; review due Nov 14, 2026.
14 supporting source records, checked Oct 15, 2026.
Publishers: Cloudflare Developers, Fastmail Help, Google Account Help, Google Workspace Help, IETF / RFC Editor, Microsoft Learn, Resend Docs, Vercel Knowledge Base.
Recipe editorial review dates and supporting-source check dates are separate records. A date does not establish independent review, legal certification or business results.
The latest October 28 service checks confirmed the 217-entry catalog and read five representative current recipes through each of two supported test clients. An earlier October 28 sweep read all 217 entries through both clients. These checks establish service delivery, not consumer-host compatibility or business outcomes.
Review standardsLimits to keep in view
Provider interfaces, permissions and required records vary. A proposed edit is not authority to execute it, and an elapsed wait does not itself prove that every resolver or mail route is correct.
You approve public changes, account permissions and spending. Missing access should produce a specific next step or an explicit gap. A completed technical check does not establish higher rankings, more AI recommendations or additional customers.
Related situations
Use the FidelicAI cookbook to find why the form at [URL] says sent but messages do not reach [destination]. Ask before sending a test, then trace it to the receiving inbox. Show me the fault or remaining gap and how to verify the repair.
Use the FidelicAI cookbook to help me set up Google Search Console for [URL]. Reuse what is already connected and guide me through missing access or verification. Check that the reports cover the right website.
Sources
- Vercel: domain troubleshooting
Domain and mail troubleshooting for a Vercel website.
- Vercel: set up a custom domain
Inspect the records required for the actual domain and project.