Public SiteGround evidence we can test
SiteGround is relevant here for Site Tools DNS, SSL, redirects and email DNS. The scanner does not sign in to the account; it compares the public-facing configuration associated with Site Tools, DNS Zone Editor, SSL Manager, Email so a provider dashboard and the Internet-visible result can be checked against one another.
- Site Tools — Verify Site Tools from the public Internet and compare it with the value the responsible provider says should be live.
- DNS Zone Editor — Verify DNS Zone Editor from the public Internet and compare it with the value the responsible provider says should be live.
- SSL Manager — Test the hostname actually requested, its certificate dates and SAN coverage, and the TLS handshake. Root and www can serve different certificates.
- Email — Verify Email from the public Internet and compare it with the value the responsible provider says should be live.
Where SiteGround changes normally belong
SiteGround Site Tools for Domain/DNS, Security/SSL and Email configuration. Before editing that area, verify that SiteGround actually controls the failing layer; a domain may use a different company for authoritative DNS, mail or the origin application.
How to interpret SiteGround detection
Site Tools and DNS Zone Editor can support a SiteGround identification, but signatures are confidence-weighted. If the visible address belongs to a CDN/reverse proxy, the edge provider is reported as the edge and the hidden origin is not guessed. Mail-provider signatures likewise identify public routing, not private account ownership.
Common SiteGround change points
Site Tools DNS, SSL, redirects and email DNS most often breaks after a domain connection, nameserver move, website migration, certificate/HTTPS change or mail-DNS edit. For this provider, compare Site Tools, DNS Zone Editor, SSL Manager with the value expected for the exact domain and account before replacing a working setting elsewhere.
Repair SiteGround without widening the incident
Save the current public value, change only the setting tied to the diagnosis, and preserve unrelated working records. If DNS is not authoritative at SiteGround, make the DNS edit at the provider named by the active nameservers. If SiteGround owns only hosting or mail, leave the other service layers where they are.
Verify the SiteGround repair
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. The verification should use the exact hostname/service repaired and should no longer depend on a control-panel “connected” indicator once the public check is available.
What a public scan cannot see inside SiteGround
Billing state, private support actions, unpublished incidents, private origin addresses and authenticated account settings are outside a public diagnostic. HostWithShery reports those areas as unknown or a next support step instead of manufacturing certainty from a weak SiteGround signature.
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.