Brian - TGL

You can set up the local DNS in your hosts file:

https://www.howtogeek.com/howto/27350/beginner-geek-how-to-edit-your-hosts-file/

in WP if you entered the siteurl as mywordpress.com in your hosts file you would have the local IP info in your hosts file of:

192.168.0.50 mywordpress.com

Which 2 pages, in particular, do you see the mobile issue on?

Do you have a site address you can share?

So your potential customers would come to your website, enter the details of what they require from you and submit them, and you would receive the details and give them a price for services?

Do you have the website address you could share?

It doesn’t appear as though WordPress is installed in the root of that directory.

What steps did you take during the installation process?

https://en.support.wordpress.com/contact/

the option for “WordPress.com Customer Support” should get you in touch with the support you need

Just verifying the plugin you used: https://www.ads-software.com/plugins/duplicator/

What were the steps you took?

When your hosting company suspended the site I assume you still had access to the admin?

Be sure you are still logged in to your site, I haven’t seen any documentation about the removal of the admin bar (top menu) but it is possible that a plugin you are using could be causing an issue.

If you deactivate your plugins one by one and try going to the main site page when you are logged in, you can check each plugin.

There are two parts to that remediation section, the first offers a server solution to use the canonical name, but the second is WP could use home or siteurl instead of SERVER_NAME to solve it for every install regardless of server flavour.

If looking up the SERVER_NAME/host is the vulnerability in both instances wouldn’t it make sense to instead use the configured value, or is there some benefit at the WP end to using SERVER_NAME in wp-includes/pluggable.php?