Who hosts it
A host that names itself in the answer, else the owner of the network the address belongs to, with the reverse DNS name and the nameservers. A CDN in front is named, and then we say the server behind it is hidden.
Free tool
Type a site's address and see who hosts it, what the server runs, how fast it starts answering, and whether the connection is secure and current. Then a plain verdict: does this hosting fit a store? Free, no email, a few seconds.
We keep the address and the answer for a few hours. Nothing about you.
What it checks
A host that names itself in the answer, else the owner of the network the address belongs to, with the reverse DNS name and the nameservers. A CDN in front is named, and then we say the server behind it is hidden.
The web server software and the PHP version when the server shows them, checked against php.net's supported versions.
HTTP/2 and HTTP/3, the TLS version and how long the certificate is still valid.
Three reads of the home page from our server in Europe; we take the time the server needs before it starts answering and show the middle one, against Google's own bands.
What the verdict means
We never mark a host good or bad by its name.
Three ways, in this order. Some hosts name themselves in the server's answer. Otherwise the site's address belongs to a network, and the internet registries record who owns that network. The reverse DNS name of the address often says the same. When a CDN like Cloudflare sits in front, the real server is hidden, and we say so instead of guessing.
Google calls a time to first byte of 0.8 seconds or less good and more than 1.8 seconds poor. We measure the part the server spends before it starts answering, three times, and show the middle one. A store page that cannot be cached, like the cart or the checkout, is often slower than the home page.
Most well-run servers do not announce their PHP version, which is a good habit. When a server does show it, we check it against php.net's list of supported versions.
They are newer versions of the protocol browsers use to fetch a page. HTTP/2 lets a browser get all of a page's files over one connection at the same time, which helps a store with many images and scripts. Every current server supports it. HTTP/3 is newer still and mostly offered by CDNs.
Not by itself. What matters is how fast the server answers, whether its software still gets security fixes, and how it copes when many shoppers arrive at once. We judge the first two from outside. The last one only shows in a load test or on a busy day.
The site address and the answer, for a few hours, so a repeat check is instant. Nothing about you. Your network address is used only to limit how many checks one visitor can run in an hour.
A second opinion
Send us the result. We tell you whether moving is worth it or whether the time is better spent elsewhere. We host stores too, in the EU, from 100 € a year excl. VAT.
Related: free store audit · store speed test · hosting and pricing