Server errors during your scan (500, 502, 503, 504)
What's happening
When we tried to scan your site, the server returned an error. These are temporary issues on the server side and usually clear up on their own. The specific code tells you what kind of issue, but the fix is the same for all four.
What each code means
500 — Critical error. Something broke on the server.
502 — The server or a piece of your CDN/proxy didn't respond properly.
503 — The site is currently unavailable (maintenance, overload, or a brief outage).
504 — The server took too long to respond and we timed out.
The fix
Wait 10 minutes. Most of these errors clear up on their own.
Try scanning again.
If the same error keeps coming back, check your server logs (or ask your hosting provider or dev team to). The logs will show exactly what went wrong.
If your hosting provider has a status page, check it — sometimes the issue is on their side and they're already aware.
Common causes
Your server crashed or restarted
A database query was too slow
An external API your site depends on was slow or down
Your server hit its memory or CPU limit
Your hosting provider was doing maintenance
Still not working?
If the same server error keeps happening on repeated scans, our team has already been notified and will reach out to help. We can also try scanning at a different time of day if your site has predictable slow periods.