David Satime Wallin

BMRE Domain Monitor is built to keep an eye on the domains you add.
It checks the expiration date and warns you if a domain will expire in 30 days or less (both through email and in the admin interface)
It also has the feature (optional) to suggest domains that are similar to the ones you’ve added and that are still available.
DISCLAIMER: Do not ONLY trust this plugin for your domains. It works well but I can not be held responsible if something should go wrong and your domain does actually expire.
LICENSE:This program is free software: you can redistribute it and/or modify 
 it under the terms of the GNU General Public License as published by 
 the Free Software Foundation, either version 3 of the License, or 
 (at your option) any later version.
<pre><code>This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
</code></pre>

BMRE Domain Monitor

This plugin is meant to monitor your domainnames and warn you before they expire.

Joeri van Veen

Easily manage a large number of landing pages or small websites from a single WordPress site.
This plugin offers an easy way to map different domains to different landing pages on your WordPress site. Now you can easily maintain a large number of small sites from a single WordPress installation.
You don’t have to set anything up, it works out of the box.
Just point a domain that you own to your WordPress installation. In WordPress, create a page for that domain. The slug should be the domain name without ‘www’ and with the <code>.</code>’s replaced by hyphens.
You can see it working on my own domain: wp-developer.eu, which shows a special page with slug <code>wp-developer-eu</code> on my joerivanveen.com blog (joerivanveen.com/blog/wp-developer-eu is the same).
<h4>Benefits:</h4>
<ol>
<li>
Easily reuse and maintain elements like forms on several domains at once.
</li>
<li>
Bring in more traffic using landing pages for multiple domains without hassle.
</li>
<li>
Favicon support for each domain, fallback from child pages to parents.
</li>
<li>
Support for custom post types, e.g. FAQ posts, portfolio posts.
</li>
<li>
The rest of your website keeps working as usual.
</li>
</ol>
<h4>Caveats:</h4>
<ul>
<li>
Some themes use webfonts, for them to work a couple of lines are added to your <code>.htaccess</code>, these are clearly marked #ruigehond007 (this is my seventh plugin).
</li>
<li>
If your blog is in a subfolder of the main site (e.g. my-site.com/blog) you need to take an extra step for this to work, see installation tab.
</li>
<li>
Not all custom post types are guaranteed to work as landing page, e.g. WooCommerce products need additional work to be able to access the main cart.
</li>
<li>
If you need more flexibility (and more work) there is WordPress Multisite.
</li>
</ul>
I put special care in making the plugin very lightweight, you will notice it has virtually no effect on the speed of your installation.
<h3>Favicons</h3>
Switch on <code>with_favicon</code> on the settings page, to allow adding favicons to each landing page (and other pages and posts as well).
Supplying the correct favicon(s) is your responsibility, the plugin will not verify their validity.
As a rule of thumb I would use a small(ish) SVG for modern browsers, and a 32×32 pixel ICO file as fallback.
You may need a plugin to be able to upload ICO and SVG files, since they are blocked by default.
<h4>.htaccess</h4>
In case the plugin was not able to update your <code>.htaccess</code>, these are the lines for your <code>.htaccess</code> to make webfonts function properly, you can add them right after ‘#END WordPress’:
<pre><code>&#35; BEGIN ruigehond007
<IfModule mod_headers.c>
<FilesMatch ".(eot|ttf|otf|woff|woff2)$">
Header set Access-Control-Allow-Origin "*"
</FilesMatch>
</IfModule>
&#35; END ruigehond007
</code></pre>
You may need to switch on headers module in your Apache configuration, if it is not already.
<h3>NGINX</h3>
NGINX does not process <code>.htaccess</code> files as standard. Best is to add the following to your nginx.conf file:
<pre><code>location ~* \.(eot|ttf|otf|woff|woff2)$ {
 add_header Access-Control-Allow-Origin *;
}
</code></pre>
Alternatively you can switch on processing of <code>.htaccess</code> files in your <code>nginx.conf</code> file. In your hosting environment this may be done by disabling ‘direct delivery’ or something similar.

Each domain a page

Five Stars!

Serves a specific page or post from WordPress depending on the domain used to access your WordPress site.

BMRE Domain Monitor vs Each domain a page