A WordPress setup screen can return HTTP 200 while leaving the site open to takeover.
Scanfully 2.5 treats a detected setup or installer screen as downtime. Once confirmed, its urgent alert bypasses quiet hours and the digest. An active snooze still applies.
Scanfully 2.5 treats a detected setup or installer screen as downtime. Once confirmed, its urgent alert bypasses quiet hours and the digest. An active snooze still applies.
1
1
0
142
See how setup-screen detection works: docs.scanfully.com/uptime/downtim…
Test Scanfully on your sites with a free 14-day trial, no card needed: app.scanfully.com/sign-up?utm_so…
Test Scanfully on your sites with a free 14-day trial, no card needed: app.scanfully.com/sign-up?utm_so…
0
0
0
21
Your WordPress site can stay online while its monitoring data goes stale.
Scanfully 2.5 checks when its plugin stops reporting and explains the reason when it can.
Uptime, certificate, and DNS checks continue. The missing WordPress data gets a warning.
Scanfully 2.5 checks when its plugin stops reporting and explains the reason when it can.
Uptime, certificate, and DNS checks continue. The missing WordPress data gets a warning.
1
0
0
42
See the connection checks and fixes: docs.scanfully.com/sites/plugin-c…
Try Scanfully free for 14 days, no credit card needed: app.scanfully.com/sign-up?utm_so…
Try Scanfully free for 14 days, no credit card needed: app.scanfully.com/sign-up?utm_so…
0
0
0
14
Retired a page while it was down? Removing it from monitoring now ends that downtime in Scanfully. The removed page no longer leaves the site degraded or distorts the next recovery's duration.
We fixed this in 2.5.0.
docs.scanfully.com/changelog/#250…
We fixed this in 2.5.0.
docs.scanfully.com/changelog/#250…
1
0
0
18
Managing uptime across WordPress sites? Sign up and test Scanfully:
app.scanfully.com/sign-up
app.scanfully.com/sign-up
0
0
0
11
“Your site is down” leaves you with the diagnosis.
Scanfully 2.5 names detected WordPress errors, database errors, timeouts, and connection failures in the alert, with a next step.
When PHP exposes the error, it can also name the plugin or theme.
Scanfully 2.5 names detected WordPress errors, database errors, timeouts, and connection failures in the alert, with a next step.
When PHP exposes the error, it can also name the plugin or theme.
1
1
0
115
See what's changed: docs.scanfully.com/changelog/?utm…
Try Scanfully free for 14 days, no credit card needed: app.scanfully.com/sign-up?utm_so…
Try Scanfully free for 14 days, no credit card needed: app.scanfully.com/sign-up?utm_so…
0
0
1
16
A scan could stay marked as running for up to two hours if it was in progress while we updated Scanfully.
We fixed that in 2.5.0, so this update-related status no longer leaves you waiting.
docs.scanfully.com/changelog/#250…
We fixed that in 2.5.0, so this update-related status no longer leaves you waiting.
docs.scanfully.com/changelog/#250…
1
1
0
116
Want to test Scanfully's monitoring on your WordPress site? Start here:
app.scanfully.com/sign-up
app.scanfully.com/sign-up
0
0
0
18
Scanfully retweeted
A notification of a failing page is great, but in reality, you want to know why that page is failing, right? Right!
Well, to remedy that, we've just updated Scanfully to read what a failing page is actually showing and include that information, with suggested next steps, in the alert.
Well, to remedy that, we've just updated Scanfully to read what a failing page is actually showing and include that information, with suggested next steps, in the alert.
Getting a “your site is down” alert usually means opening the site and the hosting panel to work out what you're dealing with. Is WordPress throwing an error, or do you need to get the host involved?
We've just updated Scanfully to read what a failing page is actually showing ation, with suggested next steps, in the alert.
So you'll see whether it's a WordPress critical error, a database connection failure, or a PHP fatal error. Where the page exposes the PHP error details, you get the message, file, and plugin or theme involved. Updates leading up to the downtime are there too, so you can check what changed.
We've also added detection for something a status-code check can miss entirely: the WordPress setup screen.
If wp-config.php goes missing or the database gets emptied, WordPress can start offering to set itself up again. The page loads, the monitor sees a successful response, and your site can be open to takeover. Once Scanfully confirms it, the urgent alert goes out, even during quiet hours and without waiting for the daily digest.
Then there's the monitoring plugin itself. If it stops reporting, your site health, update, vulnerability, and activity data quietly gets stale. Scanfully now flags that too, identifies the reason where it can, and tells you what to check. That might be a restored backup, scheduled tasks that aren't running, or a firewall blocking the connection.
You can access this context through our MCP server as well. Connect Claude, ChatGPT, Cursor, or VS Code and ask “Why was the shop down last night, and what should I do?” or “Which of my sites stopped reporting, and why?”
A few other changes in this release:
- Downtime is counted from the first failed check across alerts, the digest, and uptime screens.
- WordPress maintenance mode gets 10 minutes, so a normal update doesn't trigger downtime.
- Timeout alerts arrive about 2 minutes sooner.
You can try Scanfully free for 14 days. No credit card needed
app.scanfully.com/sign-up
0
1
1
347
Scanfully retweeted
This was very interesting to build. Most of the times it's as simple as 2XX code = site works. But there's some weird, and potentionally dangerous, edge cases.
Getting a “your site is down” alert usually means opening the site and the hosting panel to work out what you're dealing with. Is WordPress throwing an error, or do you need to get the host involved?
We've just updated Scanfully to read what a failing page is actually showing ation, with suggested next steps, in the alert.
So you'll see whether it's a WordPress critical error, a database connection failure, or a PHP fatal error. Where the page exposes the PHP error details, you get the message, file, and plugin or theme involved. Updates leading up to the downtime are there too, so you can check what changed.
We've also added detection for something a status-code check can miss entirely: the WordPress setup screen.
If wp-config.php goes missing or the database gets emptied, WordPress can start offering to set itself up again. The page loads, the monitor sees a successful response, and your site can be open to takeover. Once Scanfully confirms it, the urgent alert goes out, even during quiet hours and without waiting for the daily digest.
Then there's the monitoring plugin itself. If it stops reporting, your site health, update, vulnerability, and activity data quietly gets stale. Scanfully now flags that too, identifies the reason where it can, and tells you what to check. That might be a restored backup, scheduled tasks that aren't running, or a firewall blocking the connection.
You can access this context through our MCP server as well. Connect Claude, ChatGPT, Cursor, or VS Code and ask “Why was the shop down last night, and what should I do?” or “Which of my sites stopped reporting, and why?”
A few other changes in this release:
- Downtime is counted from the first failed check across alerts, the digest, and uptime screens.
- WordPress maintenance mode gets 10 minutes, so a normal update doesn't trigger downtime.
- Timeout alerts arrive about 2 minutes sooner.
You can try Scanfully free for 14 days. No credit card needed
app.scanfully.com/sign-up
1
2
2
173
Which requests in your server logs are ours? Look for Scanfully in the user agent. Since 2.4.8, our checks identify themselves there.
Use it to filter logs, not to allow firewall access. The user agent can be copied.
docs.scanfully.com/general/scanfu…
Use it to filter logs, not to allow firewall access. The user agent can be copied.
docs.scanfully.com/general/scanfu…
1
0
0
57
Want to test Scanfully on your WordPress site? Sign up here:
app.scanfully.com/sign-up
app.scanfully.com/sign-up
0
0
0
19
Getting a “your site is down” alert usually means opening the site and the hosting panel to work out what you're dealing with. Is WordPress throwing an error, or do you need to get the host involved?
We've just updated Scanfully to read what a failing page is actually showing ation, with suggested next steps, in the alert.
So you'll see whether it's a WordPress critical error, a database connection failure, or a PHP fatal error. Where the page exposes the PHP error details, you get the message, file, and plugin or theme involved. Updates leading up to the downtime are there too, so you can check what changed.
We've also added detection for something a status-code check can miss entirely: the WordPress setup screen.
If wp-config.php goes missing or the database gets emptied, WordPress can start offering to set itself up again. The page loads, the monitor sees a successful response, and your site can be open to takeover. Once Scanfully confirms it, the urgent alert goes out, even during quiet hours and without waiting for the daily digest.
Then there's the monitoring plugin itself. If it stops reporting, your site health, update, vulnerability, and activity data quietly gets stale. Scanfully now flags that too, identifies the reason where it can, and tells you what to check. That might be a restored backup, scheduled tasks that aren't running, or a firewall blocking the connection.
You can access this context through our MCP server as well. Connect Claude, ChatGPT, Cursor, or VS Code and ask “Why was the shop down last night, and what should I do?” or “Which of my sites stopped reporting, and why?”
A few other changes in this release:
- Downtime is counted from the first failed check across alerts, the digest, and uptime screens.
- WordPress maintenance mode gets 10 minutes, so a normal update doesn't trigger downtime.
- Timeout alerts arrive about 2 minutes sooner.
You can try Scanfully free for 14 days. No credit card needed
app.scanfully.com/sign-up
We've just updated Scanfully to read what a failing page is actually showing ation, with suggested next steps, in the alert.
So you'll see whether it's a WordPress critical error, a database connection failure, or a PHP fatal error. Where the page exposes the PHP error details, you get the message, file, and plugin or theme involved. Updates leading up to the downtime are there too, so you can check what changed.
We've also added detection for something a status-code check can miss entirely: the WordPress setup screen.
If wp-config.php goes missing or the database gets emptied, WordPress can start offering to set itself up again. The page loads, the monitor sees a successful response, and your site can be open to takeover. Once Scanfully confirms it, the urgent alert goes out, even during quiet hours and without waiting for the daily digest.
Then there's the monitoring plugin itself. If it stops reporting, your site health, update, vulnerability, and activity data quietly gets stale. Scanfully now flags that too, identifies the reason where it can, and tells you what to check. That might be a restored backup, scheduled tasks that aren't running, or a firewall blocking the connection.
You can access this context through our MCP server as well. Connect Claude, ChatGPT, Cursor, or VS Code and ask “Why was the shop down last night, and what should I do?” or “Which of my sites stopped reporting, and why?”
A few other changes in this release:
- Downtime is counted from the first failed check across alerts, the digest, and uptime screens.
- WordPress maintenance mode gets 10 minutes, so a normal update doesn't trigger downtime.
- Timeout alerts arrive about 2 minutes sooner.
You can try Scanfully free for 14 days. No credit card needed
app.scanfully.com/sign-up
0
1
2
655
Scanfully retweeted
We're looking for Beta users for @Scanfullyapp's new WooCommerce Monitoring!
If you run a WooCommerce store for your clients, or for yourself, we'd love to have you testing us and your feedback!
Learn more about what our WooCommerce Monitoring does: docs.scanfully.com/woocommerce/
If you run a WooCommerce store for your clients, or for yourself, we'd love to have you testing us and your feedback!
Learn more about what our WooCommerce Monitoring does: docs.scanfully.com/woocommerce/
0
3
3
493
Scanfully retweeted
Yesterday's PHP fix doesn't reach PHP 8.1 or older. Those branches get no security releases, and CERT-EU says every version from PHP 5 on could be affected.
Scanfully flags them on every site:
→ end of life: critical
→ behind the latest release: warning
Upgrade those first.
Scanfully flags them on every site:
→ end of life: critical
→ behind the latest release: warning
Upgrade those first.
2
2
1
192
Scanfully retweeted
We added a spiffy little filter on top of Scanfully's WordPress Activity Log:
0
2
12
620
With version 2.3, we’ve rebuilt Scanfully’s activity log to help you find that history faster. Search, category tabs, a Who filter, and date controls make it easier to narrow down the relevant events.
1
2
0
206
Or... users with elevated permissions, Scanfully records successful logins, password and email changes, and application-password activity. That includes application passwords being created, revoked, or used for the first time.
Login events include the IP address and browser, giving you more context when reviewing access.
Login events include the IP address and browser, giving you more context when reviewing access.
1
0
0
5
Update the Scanfully plugin to version 1.9.0 or later to receive the new events.
We’ve covered the changes and how they fit together in the blog post.
scanfully.com/scanfully-2-3-…
We’ve covered the changes and how they fit together in the blog post.
scanfully.com/scanfully-2-3-…
0
0
0
9