Protect

This feature can be enabled by switching on “Brute force attack protection” at Jetpack → Settings → Security in your site’s wp-admin Dashboard.

For issues with Protect, visit the troubleshooting section.

Jetpack Protect allows you to protect yourself against traditional brute force attacks and distributed brute force attacks that use many servers against your site.

Jetpack’s botnet security features work automatically when you install Jetpack and connect Jetpack to your WordPress.com account. With botnet protection in place via Jetpack Protect, your site will block unwanted login attempts.

You can view a count of attacks to your site with a widget in your self-hosted site’s dashboard.

Jetpack Protect Widget

Let’s look into what we can do for your Jetpack sites from this new interface.

Settings

Whitelisting Your IP Address

Whitelisting may be necessary if you’ve made too many failed log in attempts to your site. There are three methods for whitelisting your IP address:

  • If you have access to your site and you’ve not been blocked, you can enter your IP or IPv6 address(es) by going to Jetpack → Settings → Security → Brute force attack protection.
  • If you are blocked from entering your site, you can enter the IP or IPv6 address(es) via WordPress.com by visiting My Sites → Manage → Settings → Security → Prevent brute force login attacks.
  • You can also whitelist one IP address by setting it as the JETPACK_IP_ADDRESS_OK constant in your wp-config.php like this: define('JETPACK_IP_ADDRESS_OK', 'X.X.X.X');

You can find your IP by visiting any of the following sites:

Jetpack Protect Settings

Troubleshooting Information and FAQs

Are you unable to enable the Protect module on your site? Check the tips below to find out why.

Why am I seeing a math captcha on my login page?

The math captcha is used as a fallback for the protect feature. If your IP has been blocked due to too many failed login attempts, you may still access your site by correctly filling out the math captcha along with the correct login credentials. In very rare cases, you might see the captcha if you’ve not obtained an API key or during times of very heavy attacks.

How long is an IP blocked?

The length of time is based on a number of factors and is not a set amount of time.

Jetpack Protect is unable to effectively protect your site because your server is misconfigured

Whenever someone tries to log in to your site, Jetpack’s Protect module looks at that person’s IP address and compares it with our global database of malicious IP addresses.

For this to work properly, we rely on IP addresses stored and provided by your server. Unfortunately in some cases your server may not return any IP address, thus blocking Protect from working properly. When this happens, the Protect module will be disabled and we will let you know.

If that happens, do not hesitate to send a link to this page to your hosting provider, so they can take a look and fix the issue for you. They can also contact us directly via this contact form if they need more information.

Unblock yourself when your IP address was blocked by Jetpack’s Protect module

If you tried to log in to your site multiple times but failed to log in because you had forgotten your password, you may end up being blocked by Jetpack’s Protect module.

In this case, you’ll see something like this:

protect-locked

Enter your email address and hit Send. You will receive an email with a special link you can click to regain access to the login form. If you get an error when clicking the link in the email, you can follow one of the three methods described here to unblock yourself. If you are still blocked, it’s likely due to a configuration issue on your server. Please contact us for help fixing that.

Protect on Multisite Networks

If you tried to log in to your site multiple times but failed to log in because you had forgotten your password, you may end up being blocked by Jetpack’s Protect module.

In a WordPress Multisite installation, you can log in to any account that exists on the network through any log in page on the network.  As a result, if you have Jetpack Protect active on some sites but not all, then no site is truly being protected.

To address this, please network enable Jetpack on your multisite installation and activate the Protect feature on the network’s primary site.  Once completed, Jetpack’s Protect feature will be activated on every site on your network, even if Jetpack isn’t connected on those sites.

Protect reports thousands of blocked malicious login attempts

The best way to explain this feature is that there are thousands of “bots” out there trying to gain access to sites all over the internet. No matter what size your site is, there’s always someone or something trying to “break in”. WordPress is very secure and usually the weakest point is someone’s password. Bots consequently try to guess people’s passwords to get in.

Jetpack’s Protect module collects information from failed attempts from millions of sites and protects you from these attacks. For example, if a bot tried to gain access to site A, and then went to site B, Protect would already know who this bot is and before it even tries to get into site B, it would be blocked.

Along with that, it’s also really important to have strong secure passwords.

Find out more information about the Protect feature here.

Privacy Information (Protect)

This feature is activated by default. It can be deactivated any time by toggling the Protect setting in the Security section from Jetpack — Dashboard — At a Glance in your dashboard.

More information about the data usage on your site
Data Used
Site Owners / Users

In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user’s IP address, attempting user’s email address/username (i.e. according to the value they were attempting to use during the login process), and all IP-related HTTP headers attached to the attempting user.

Additionally, for activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.

Site Visitors

In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user’s IP address, attempting user’s email address/username (i.e. according to the value they were attempting to use during the login process), and all IP-related HTTP headers attached to the attempting user.

Activity Tracked
Site Owners / Users

Failed login attempts.

We track when, and by which user, the feature is activated and deactivated. We also set a cookie (jpp_math_pass) for 1 day to remember if/when a user has successfully completed a math captcha to prove that they’re a real human. Learn more about this cookie.

Site Visitors

Failed login attempts.

We set a cookie (jpp_math_pass) for 1 day to remember if/when a user has successfully completed a math captcha to prove that they’re a real human. Learn more about this cookie.

Data Synced (Read More)
Site Owners / Users

Options that identify whether or not the feature is activated and how its available settings are configured. We also sync the site’s whitelisted entries (as configured by the site owners), the Protect-specific API key used for login checking, and any failed login attempts, which contain the user’s IP address, attempted username or email address, and user agent information.

Site Visitors

Failed login attempts, which contain the user’s IP address, attempted username or email address, and user agent information.

Comments Off on Protect

Security Scanning

Jetpack Premium and Professional plans include daily, automated security scanning and one-click threat resolution. On this page, you’ll learn about some of the more common threats that we look for and how to properly address them.

Changes to Core WordPress Files

We checks you WordPress installation to see if any core files have been changed or deleted. Generally, these files should never be changed, so please keep that in mind when working on your site. WordPress functionality can and should be altered by using plugins and themes instead.

If you didn’t make the changes to your core files, you should consider the files suspicious and consider replacing them. If you’re unsure of the changes you see, you can always contact us.

Web-Based Shells

Web-based shells give an attacker full access to your server — allowing them to execute malicious code, delete files, make changes to your database, and many more dangerous things.

Shells are usually found in files, and they can be removed by deleting any infected files from your server and replacing them with a clean version from your backup. If you don’t have a clean backup, or have any questions about removing shells, please get in touch.

TimThumb Vulnerability

TimThumb is a popular script that allows users to resize images on the fly. Since it is sometimes present within themes and plugins, you might not even know you’re running it.

Older versions of TimThumb may include a vulnerability that allows third parties to upload and execute malicious code in the TimThumb cache directory.

The simplest way to repair this vulnerability is to update all copies of TimThumb to the latest version. Alternatively, you could delete all copies of TimThumb from your server. You can also use our repair feature shown here:

Tim Thumb Repair

By hitting repair, this will fix the vulnerability for you. Please note that deactivating a theme or plugin which uses TimThumb does not fix the vulnerability.

If you have any questions about security threats or suspicious code, you’re always welcome to contact us.

Privacy Information

This feature is deactivated by default, and requires an upgrade to the Premium or Professional plan to unlock/activate.

Data Used
Site Owners / Users

None.
Site Visitors

None.
Activity Tracked
Site Owners / Users

None.
Site Visitors

None.
Data Synced (Read More)
Site Owners / Users

None.
Site Visitors

None.
Comments Off on Security Scanning

Troubleshooting issues with the Protect module

Are you unable to enable the Protect module on your site? Check these tips to find out why.

Jetpack Protect is unable to effectively protect your site because your server is misconfigured

Whenever someone tries to log in to your site, Jetpack’s Protect module looks at that person’s IP address and compares it with our global database of malicious IP addresses.

For this to work properly, we rely on IP addresses stored and provided by your server. Unfortunately in some cases your server may not return any IP address, thus blocking Protect from working properly. When this happens, the Protect module will be disabled and we will let you know.

If that happens, do not hesitate to send a link to this page to your hosting provider, so they can take a look and fix the issue for you. They can also contact us directly via this contact form if they need more information.

Unblock yourself when your IP address was blocked by Jetpack’s Protect module

If you tried to log in to your site multiple times but failed to log in because you had forgotten your password, you may end up being blocked by Jetpack’s Protect module.

In this case, you’ll see something like this:

protect-locked

Enter your email address and hit Send. You will receive an email with a special link you can click to regain access to the login form. If you get an error when clicking the link in the email, you can follow one of the three methods described here to unblock yourself. If you are still blocked, it’s likely due to a configuration issue on your server. Please contact us for help fixing that.

Protect on Multisite Networks

In a WordPress Multisite installation, you can log in to any account that exists on the network through any log in page on the network.  As a result, if you have Jetpack Protect active on some sites but not all, then no site is truly being protected.

To address this, please network enable Jetpack on your multisite installation and activate the Protect feature on the network’s primary site.  Once completed, Jetpack’s Protect feature will be activated on every site on your network, even if Jetpack isn’t connected on those sites.

Protect reports thousands of blocked malicious login attempts

The best way to explain this feature is that there are thousands of “bots” out there trying to gain access to sites all over the internet. No matter what size your site is, there’s always someone or something trying to “break in”. WordPress is very secure and usually the weakest point is someone’s password. Bots consequently try to guess people’s passwords to get in.

Jetpack’s Protect module collects information from failed attempts from millions of sites and protects you from these attacks. For example, if a bot tried to gain access to site A, and then went to site B, Protect would already know who this bot is and before it even tries to get into site B, it would be blocked.

Along with that, it’s also really important to have strong secure passwords.

Find out more information about the Protect feature here.

If you have more questions, do not hesitate to contact us!

Comments Off on Troubleshooting issues with the Protect module

Security

Jetpack includes state-of-the-art security tools that keep your site safe and sound, from posts to plugins.

Are you blocked from accessing your dashboard? Use one of the three methods described here to unblock yourself.

Here are some resources to help get you started:

  • Protect - Jetpack Protect allows you to protect yourself against traditional brute force attacks and distributed brute force attacks that use many servers against your site
  • Security Scanning - Jetpack Premium and Professional plans include daily, automated security scanning and one-click threat resolution. On this page, you’ll learn about some of the more common threats that we look for and how to properly address them. Changes to Core WordPress Files We checks you WordPress installation to see if any core files have been changed […]
  • Troubleshooting issues with the Protect module - Are you unable to enable the Protect module on your site? Check these tips to find out why.
  • Security - Jetpack includes state-of-the-art security tools that keep every bit of your site safe and sound.
  • Security Features - Jetpack’s security features allow you to secure your self-hosted WordPress sites from a single dashboard on WordPress.com.
  • WordPress.com Secure Sign On - Using the same log-in credentials you use for WordPress.com, you’ll now be able to register for and sign in to self-hosted WordPress.org sites quickly and securely.
  • Downtime Monitoring - Jetpack Monitor will keep tabs on your site, and alert you the moment that downtime is detected.

Our paid subscriptions offer even more ways to protect and monitor your site — learn more here.

Privacy Information

Comments Off on Security

Security Features

Jetpack Security FeaturesJetpack includes state-of-the-art security tools that keep your site safe and sound, from posts to plugins.

Jetpack’s Security features include:

Are you blocked from accessing your dashboard? Use one of the three methods described here to unblock yourself.

Here are some resources to help get you started:

  • Protect - Jetpack Protect allows you to protect yourself against traditional brute force attacks and distributed brute force attacks that use many servers against your site
  • Security Scanning - Jetpack Premium and Professional plans include daily, automated security scanning and one-click threat resolution. On this page, you’ll learn about some of the more common threats that we look for and how to properly address them. Changes to Core WordPress Files We checks you WordPress installation to see if any core files have been changed […]
  • Troubleshooting issues with the Protect module - Are you unable to enable the Protect module on your site? Check these tips to find out why.
  • Security - Jetpack includes state-of-the-art security tools that keep every bit of your site safe and sound.
  • Security Features - Jetpack’s security features allow you to secure your self-hosted WordPress sites from a single dashboard on WordPress.com.
  • WordPress.com Secure Sign On - Using the same log-in credentials you use for WordPress.com, you’ll now be able to register for and sign in to self-hosted WordPress.org sites quickly and securely.
  • Downtime Monitoring - Jetpack Monitor will keep tabs on your site, and alert you the moment that downtime is detected.

Our paid subscriptions offer even more ways to protect and monitor your site — learn more here.

Troubleshooting information and FAQs

What else should I do to protect my sites?

Backups

It’s strongly recommended you back up your self-hosted sites using a tool such as VaultPress. Backups provide a recovery mechanism should a malicious file corrupt your site or become otherwise compromised.

Updates

Jetpack’s Plugin Updates feature makes it easy to keep your plugins up to date. By setting your plugins to auto-update, you help ensure any issues that may arise due to plugins with malicious code will not harm your site.

Keeping your plugins and themes updated is one of the most effective ways to keep your self-hosted WordPress sites secure. By using Jetpack’s Site Management tools, you can keep your plugins up to date from one easy control panel in WordPress.com. Learn more about Jetpack’s plugin updates»

Monitor

Jetpack’s site monitoring feature will keep tabs on your site and alert you the moment downtime is detected. Monitoring uptime of your site can be an important tool in the security of your site. Learn more about Jetpack’s Monitor»

Privacy Information

Comments Off on Security Features

Downtime Monitoring

Jetpack’s downtime monitor will continuously watch your site, and alert you the moment that downtime is detected.

Once activated, one of our servers will start checking your site every five minutes.  If it looks like something’s gone awry, we’ll fire off an email notification to the WordPress.com account that Jetpack is connected to.


Emails

When downtime monitoring is activated, downtime notification emails will be sent to the user who activated it. If you have additional admin users connected to their WordPress.com accounts, they can also enable these email notifications for themselves via Jetpack → Settings → Security.

If you’d like to add something to your email filters to make sure these notification emails never get sent to spam, they’ll all be coming from support+monitor AT jetpack DOT com.

Is your site up and running properly, but you’re receiving ‘site down’ notifications?

This can happen for different reasons, and the content of the Notification emails should tell you more.

Your site is responding intermittently, or extremely slowly.

Your site may be loading slowly. If your site can’t be loaded in less than 20 seconds, we consider it as inaccessible. This may happen if you’re on shared hosting, where your bandwidth is shared with many other websites, or if you have a lot of resources loading on your home page; this will slow your site down.

Note that in some cases your site may be slow for a few minutes only. Its loading speed then comes back to normal after your hosting provider has taken measures to isolate other sites on your server that may have used too many resources and slowed everyone else’s site down for a few minutes.

Our requests are being redirected too many times.

If this happens, make sure your site URL is properly set up and that you don’t use any redirection plugins that may cause issues.

Jetpack is blocked.

Make sure your hosting service isn’t blocking our monitoring agent! The user agent that we’re sending along with the HEAD requests should be jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)! If it’s still not going through properly, please contact support.

The server does not respond..

If your theme or one of your plugins create 500 errors, also known as Fatal Errors, on your site, readers won’t be able to access your site and we will send you an email to let you know..

How does this work behind the scenes?

When we check your site, we ping your site’s homepage (via a HTTP HEAD request) every five minutes.

We tentatively mark your site as down if the HTTP response code is 400 or greater, which indicates either a permissions error or a fatal code error is prohibiting your site from appearing to visitors, or we see more than three 300-series redirects, suggesting a redirect loop, or if your site fails to respond within 20 seconds.

Once it is tentatively marked down, we then spin up three separate servers in geographically different locations from a third-party vendor to ensure the problem is not isolated to our network or the location of our primary datacenter.

If all three checks fail, we mark the site as down and notify you.

Note: Jetpack uses the timezone set in your WordPress settings (Settings > General)

Privacy Information

This feature is deactivated by default. If you ever need to deactivate this feature, you can click on the Settings link in the Downtime Monitoring section from Jetpack — Dashboard — At a Glance in your dashboard. Once you’re viewing the feature’s settings on WordPress.com, toggle the Monitor your site’s downtime setting found within the Downtime Monitoring section at the top of the page.

More information about the data usage on your site

This feature is deactivated by default. If you ever need to deactivate this feature, you can click on the Settings link in the Downtime Monitoring section from Jetpack — Dashboard — At a Glance in your dashboard. Once you’re viewing the feature’s settings on WordPress.com, toggle the Monitor your site’s downtime setting found within the Downtime Monitoring section at the top of the page.

Data Used
Site Owners / Users

Site owner’s local user ID, WordPress.com user ID, email address, WordPress.com-connected blog ID, and the date of the last downtime status change.

Additionally, for activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.

Site Visitors

None.

Activity Tracked
Site Owners / Users

We track when, and by which user, the feature is activated and deactivated. We also track when, and which, configuration settings are modified.

Site Visitors

None.

Data Synced (Read More)
Site Owners / Users

We sync options that identify whether or not the feature is activated and how its available settings are configured.

Site Visitors

None.

Comments Off on Downtime Monitoring
  • Enter your email address to follow this blog and receive news and updates from Jetpack!

    Join 106,575 other followers

  • Our most popular posts

  • Browse by topic

  • Unlimited Video Hosting

    Jetpack Premium now provides unlimited use of our video CDN. Save on hosting storage and bandwidth costs by streaming fast, ad-free video from our global network.

    Learn More