Public Plesk evidence we can test
Plesk is relevant here for DNS, hosting settings, mail service and certificate management. The scanner does not sign in to the account; it compares the public-facing configuration associated with DNS Settings, Hosting & DNS, Mail, SSL/TLS Certificates so a provider dashboard and the Internet-visible result can be checked against one another.
- DNS Settings — Verify DNS Settings from the public Internet and compare it with the value the responsible provider says should be live.
- Hosting & DNS — Verify Hosting & DNS from the public Internet and compare it with the value the responsible provider says should be live.
- Mail — Verify Mail from the public Internet and compare it with the value the responsible provider says should be live.
- SSL/TLS Certificates — Test the hostname actually requested, its certificate dates and SAN coverage, and the TLS handshake. Root and www can serve different certificates.
Where Plesk changes normally belong
Plesk Websites & Domains, DNS Settings, Mail and SSL/TLS Certificates for the affected domain. Before editing that area, verify that Plesk actually controls the failing layer; a domain may use a different company for authoritative DNS, mail or the origin application.
How to interpret Plesk detection
DNS Settings and Hosting & DNS can support a Plesk 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 Plesk change points
DNS, hosting settings, mail service and certificate management most often breaks after a domain connection, nameserver move, website migration, certificate/HTTPS change or mail-DNS edit. For this provider, compare DNS Settings, Hosting & DNS, Mail with the value expected for the exact domain and account before replacing a working setting elsewhere.
Repair Plesk 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 Plesk, make the DNS edit at the provider named by the active nameservers. If Plesk owns only hosting or mail, leave the other service layers where they are.
Verify the Plesk 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 Plesk
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 Plesk 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.