<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IP unblocking - Matteo Cisilino</title>
	<atom:link href="https://www.cisilino.com/en/tag/ip-unblocking/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.cisilino.com/en/</link>
	<description>Guide su WordPress, server e sicurezza</description>
	<lastBuildDate>Thu, 05 Nov 2026 08:04:34 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<item>
		<title>WordPress IP whitelist: manual unblocking and timed bans</title>
		<link>https://www.cisilino.com/en/2026/11/05/wordpress-ip-whitelist/</link>
					<comments>https://www.cisilino.com/en/2026/11/05/wordpress-ip-whitelist/#respond</comments>
		
		<dc:creator><![CDATA[matteocisilino]]></dc:creator>
		<pubDate>Thu, 05 Nov 2026 08:00:00 +0000</pubDate>
				<category><![CDATA[csdn]]></category>
		<category><![CDATA[IP blocking]]></category>
		<category><![CDATA[IP unblock]]></category>
		<category><![CDATA[IP unblocking]]></category>
		<category><![CDATA[IP whitelist]]></category>
		<category><![CDATA[WordPress login]]></category>
		<guid isPermaLink="false">https://www.cisilino.com/?p=161</guid>

					<description><![CDATA[<p>How to use the IP whitelist in WordPress: one-click unblocking of IPs blocked by mistake and manual timed bans that expire automatically.</p>
<p>The post <a href="https://www.cisilino.com/en/2026/11/05/wordpress-ip-whitelist/">WordPress IP whitelist: manual unblocking and timed bans</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>Every automatic defence sooner or later blocks the wrong person. The customer who gets the password wrong five times. The receptionist behind the same IP as the whole office. You yourself while testing a login. That is why the plugin has a <strong>WordPress IP whitelist</strong> and two ways to step in by hand.</p>
<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" src="https://www.cisilino.com/wp-content/uploads/2026/10/ip-whitelist-wordpress.webp" alt="WordPress IP whitelist: a purple circle with a check mark at the centre, surrounded by six smaller circles" width="1200" height="630"/></figure>
<h2>The WordPress IP whitelist: it doesn&#8217;t even count as an attempt</h2>
<p>An IP in the WordPress IP whitelist is not counted among the failed attempts. This is different from an unblock, which lifts a block that has already happened. Here the block never happens at all. It suits the office network or the service that monitors the site. The price to bear in mind is that even someone attacking from that network would not be stopped. So use it only for addresses you really control.</p>
<h2>One-click unblock</h2>
<p>The unified list gathers the IPs blocked locally, the ones received from the network and the ones added by hand. Every row, including WordPress IP whitelist entries, has its own &#8220;Unblock&#8221;.</p>
<h2>Timed ban for a specific IP</h2>
<p>Want to stop an annoying address, separate from the WordPress IP whitelist, without having to remember to lift the ban? Ban it by hand and choose the duration: permanent, 1 hour, 6 hours, 24 hours or 7 days. The same works in reverse, to unblock an address explicitly.</p>
<h2>A typical scenario</h2>
<p>An office with three workstations behind a fixed IP. All it takes is one person getting the password wrong several times and the address is blocked for everyone. Putting the office IP in the WordPress IP whitelist settles the matter.</p>
<p>A security note: every address, whatever its source, is checked as a complete IP or CIDR. This happens before it ends up in <code>.htaccess</code>. A manual override therefore cannot insert arbitrary directives into the file. For the wider picture, the official guide to <a href="https://developer.wordpress.org/advanced-administration/security/hardening/" target="_blank" rel="noopener">WordPress security hardening</a> is worth a read.</p>
<h2>Frequently asked questions</h2>
<h3>What is the difference between the whitelist and an unblock?</h3>
<p>An unblock lifts a block that is already active. The whitelist prevents an IP from being counted as a failed attempt, so the block never happens.</p>
<h3>Can I ban an IP for just a few hours?</h3>
<p>Yes. A manual ban can be permanent or last 1 hour, 6 hours, 24 hours or 7 days.</p>
<h3>Is the WordPress IP whitelist safe for the office IP?</h3>
<p>Yes, if you really control that network. An attack starting from there would not be stopped.</p>
<h2>Read more</h2>
<ul>
<li><a href="https://www.cisilino.com/?p=83">WordPress brute force attacks: how to stop them at the login</a></li>
<li><a href="https://www.cisilino.com/?p=101">Secure WordPress user registration: roles and email</a></li>
<li><a href="https://www.cisilino.com/en/2026/10/29/cisilino-site-defense-network-security-plugin/">Cisilino Site Defense Network: the WordPress security plugin</a></li>
</ul><p>The post <a href="https://www.cisilino.com/en/2026/11/05/wordpress-ip-whitelist/">WordPress IP whitelist: manual unblocking and timed bans</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://www.cisilino.com/en/2026/11/05/wordpress-ip-whitelist/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
