HHostWithSheryWebsite & Domain Troubleshooting ToolsCheck a domain
Menu
Troubleshooting areaReviewed 2026-08-13By HostWithShery technical editorial

Provider Fixes

Follow platform-specific repair instructions for DNS, SSL, domains and business email across common providers.

Start with evidence from your own domain before changing DNS, SSL or mail settings.
Check your own configuration

Complete Website Health Check

This page is preconfigured with the Complete Website Health Check that best matches this problem.

No accountPublic evidence only
Live public check

Enter the domain only. We will test root + www, DNS, HTTPS, redirects, mail and crawler access.

No account · Public configuration only
On this page
Browse this section

Choose the provider that owns the failing layer

Every important page in this area is linked here with a normal crawlable link, so you can choose by task instead of searching through a long generic list.

Provider troubleshooting hubs

Cloudflare TroubleshootingHostWithShery checks the public signals that matter for Cloudflare: proxy status, SSL/TLS mode, DNS records, email records, 52x errors. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →cPanel TroubleshootingHostWithShery checks the public signals that matter for cPanel: Zone Editor, Email Routing, SSL/TLS, Redirects. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Plesk TroubleshootingHostWithShery checks the public signals that matter for Plesk: DNS Settings, Hosting & DNS, Mail, SSL/TLS Certificates. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Hostinger TroubleshootingHostWithShery checks the public signals that matter for Hostinger: DNS Zone Editor, nameservers, email DNS, website IP. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Namecheap TroubleshootingHostWithShery checks the public signals that matter for Namecheap: Advanced DNS, nameservers, mail settings, redirects. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →GoDaddy TroubleshootingHostWithShery checks the public signals that matter for GoDaddy: DNS Management, nameservers, forwarding, email DNS. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →SiteGround TroubleshootingHostWithShery checks the public signals that matter for SiteGround: Site Tools, DNS Zone Editor, SSL Manager, Email. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Bluehost TroubleshootingHostWithShery checks the public signals that matter for Bluehost: DNS records, domains, SSL, email. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Vercel TroubleshootingHostWithShery checks the public signals that matter for Vercel: Domains, DNS records, verification, SSL provisioning. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Netlify TroubleshootingHostWithShery checks the public signals that matter for Netlify: Domain management, Netlify DNS, external DNS, HTTPS. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Shopify TroubleshootingHostWithShery checks the public signals that matter for Shopify: third-party domain, A record, www CNAME, SSL. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Squarespace TroubleshootingHostWithShery checks the public signals that matter for Squarespace: DNS Settings, domain connection, www CNAME, email records. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Wix TroubleshootingHostWithShery checks the public signals that matter for Wix: domain connection, DNS, SSL, mailboxes. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Google Workspace TroubleshootingHostWithShery checks the public signals that matter for Google Workspace: MX, SPF, DKIM, DMARC. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Microsoft 365 TroubleshootingHostWithShery checks the public signals that matter for Microsoft 365: MX, SPF, autodiscover, domain verification. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →Zoho Mail TroubleshootingHostWithShery checks the public signals that matter for Zoho Mail: MX, SPF, DKIM, domain verification. The result separates what is confirmed from what is only likely, then points to the exact setting area that should be reviewed.Open →

Specific provider repair guides

Email stopped working after moving DNS to CloudflareRestore the mail provider records in Cloudflare DNS without changing the working website records.Open →Fix Cloudflare Error 522Confirm the correct origin IP and make sure the host allows Cloudflare connections.Open →Add Microsoft 365 SPF in cPanelEdit the existing SPF TXT record rather than creating a second SPF record.Open →Fix missing MX records in cPanelRestore the MX destination and make sure Email Routing matches the actual mail provider.Open →Fix business email DNS in PleskAlign Plesk DNS with the actual mail provider and remove stale conflicting records.Open →Fix SSL for a domain in PleskIssue or select a certificate that covers the exact root and www hostnames, then enable it on the hosting subscription.Open →Hostinger email stopped after nameserver changeRestore Hostinger Email MX and authentication records in the DNS zone that is now authoritative.Open →Hostinger domain points to old websiteUpdate only the stale website endpoints and check for a forgotten AAAA record.Open →Add Google Workspace MX records in NamecheapAdd the Google Workspace MX record in Advanced DNS and remove conflicting old mail exchangers when appropriate.Open →Fix www not working in NamecheapAdd or correct the www CNAME/host record without disturbing the apex record.Open →Fix Microsoft 365 email DNS in GoDaddyRestore Exchange Online MX and SPF records in GoDaddy DNS, preserving any additional legitimate senders in the single SPF record.Open →Fix a GoDaddy domain forwarding loopChoose one canonical redirect path and remove the duplicate forwarding rule.Open →Fix WordPress redirect loop behind Cloudflare on SiteGroundUse compatible HTTPS settings at Cloudflare and SiteGround, then keep only one canonical redirect sequence.Open →Fix www SSL on SiteGroundReissue or assign a certificate covering both hostnames and ensure DNS for www resolves to the site.Open →Bluehost email stopped after DNS changeRestore the correct MX and authentication records in the authoritative DNS zone.Open →Fix a WordPress redirect loop behind CloudflareUse a valid origin HTTPS configuration, choose a compatible Cloudflare SSL mode, and remove duplicate WordPress/plugin/server redirect rules.Open →Fix Vercel custom-domain DNSMatch the DNS record required by the Vercel project and remove conflicting records for the same hostname.Open →Fix www not working on VercelAdd both intended hostnames to the project and point DNS according to Vercel’s current domain instructions.Open →Fix a Netlify custom domain that is not workingVerify the domain assignment, DNS target and HTTPS state before changing nameservers.Open →Fix Netlify HTTPS certificate pendingCorrect DNS first, then allow certificate provisioning to complete.Open →Fix Shopify domain not connectingCorrect the apex and www records required by Shopify and remove incompatible records for those hostnames.Open →Fix Shopify www not workingCorrect the www record and confirm Shopify has the hostname attached.Open →Fix Google Workspace email on Squarespace DNSRestore Google Workspace MX and email-authentication records without changing the Squarespace website records.Open →Fix Squarespace domain connectionCompare the current DNS zone with the records Squarespace expects for the connected site.Open →Fix email after connecting a domain to WixRestore the external mail provider MX and authentication records in the active Wix DNS zone.Open →Fix Wix domain not workingConfirm whether the domain is connected by nameservers or pointing and fix only the records required by that method.Open →Google Workspace not receiving emailVerify the current Google MX record and remove stale conflicting MX values.Open →Set up SPF, DKIM and DMARC for Google WorkspacePublish a single SPF policy, enable DKIM with the Admin-console selector and deploy DMARC deliberately.Open →Fix Microsoft 365 custom-domain email not workingCompare the current MX/SPF/autodiscover records with the values shown for the domain in Microsoft 365.Open →Add or fix Microsoft 365 SPFMaintain one SPF TXT record and include spf.protection.outlook.com together with any other legitimate senders.Open →Fix Zoho Mail DNS recordsUse the exact regional Zoho records shown in the Zoho Admin Console and remove stale competing MX records.Open →Fix Zoho DKIM selector not foundCopy the selector exactly, publish the TXT value and confirm it resolves before enabling signing.Open →

Provider Fixes: what this section covers

Provider Fixes translates a confirmed technical problem into the control panel where that setting normally lives. It covers DNS providers, hosting panels, deployment platforms, website builders and mail providers without turning HostWithShery into a provider-ranking or affiliate-comparison site.

Signals that matter for provider troubleshooting

The pages here interpret business-email DNS and mail authentication evidence through the following search tasks and configuration concepts. They are included because they help separate causes, not to repeat a keyword a fixed number of times.

  • Cloudflare fixes — Verify cloudflare fixes from the public Internet and compare it with the value the responsible provider says should be live.
  • Cpanel dns — Verify cpanel dns from the public Internet and compare it with the value the responsible provider says should be live.
  • Vercel domain troubleshooting — Verify vercel domain troubleshooting from the public Internet and compare it with the value the responsible provider says should be live.

Which Provider Fixes check to start with

Choose a provider guide only after confirming the provider is actually responsible for the failed layer. A domain can use Cloudflare for DNS, Vercel for hosting and Google Workspace for mail at the same time, so one company name should not be assumed to control the whole domain.

Diagnosis first, raw evidence second

The interface surfaces the highest-impact explanation and its confidence before raw protocol output. For provider troubleshooting, that means a visitor can see what probably failed and what to change while an advanced user can still inspect the DNS, certificate, header, resolver or provider evidence behind the conclusion.

What a repaired provider troubleshooting problem should look like

Every repair path begins by checking authority and preserving working records. The guide identifies the setting area, shows what public evidence should change and returns to the relevant checker. Provider dashboards are not treated as proof when public DNS/HTTP/TLS still disagrees.

Validate the business-email DNS and mail authentication change

The public MX/authentication records should match the intended mail provider, required hostnames should resolve, and the relevant SPF/DKIM/DMARC check should no longer show the original failure. Re-run the same focused tool that exposed the problem so a dashboard status, cache or unrelated healthy signal is not mistaken for proof of the repair.

Technical references

These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.