Hi, it would also be nice to be able to track some domains that aren’t necessarily in our child sites. For example, I have some tech consulting clients where I monitor their domain accounts for them and send them reminders for renewals, but I don’t run their website (or their website doesn’t use WordPress). In these cases, it would still be nice to be able to add them to the domain checklist the same way we can do for the Advanced Uptime Monitor extension. Thanks!
1 Like
The domain updates should be aggregated and sent in one mail. Pretty much the same way it is handled in other extensions such as the vlnerability extension. Currently it floods me with 400 mails. Also, the content of these mails ends up being erroneous, if the domain could not be tracked properly. I mainly have .de domains in my portfolio, and though the whois seems to be correctly set, no proper information can be obtained as of yet.
For german .de Domains I also get no data. Date is 01.01.1970.
The problem with the lookup for AU domains seems to be that it’s using whois.aunic.net, which seems to be dead.
Can it be changed to whois.auda.org.au instead, please?
1 Like
Can we add the extensions below
club
dev
group
ninja
.co.uk TLD’s aren’t working for me.
I updated to V4. the tool reports expires in 0 days with the year 0201 or 0202
This extension appears to have introduced an error into mainwp-cli. Output of mainwp-cli commands is prefaced with the following:
WordPress database error You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near '
PRIMARY KEY (`id`)' at line 1 for query ALTER TABLE wp_mainwp_domain_monitor CH
ANGE COLUMN `last_check` `last_check` int(11) NOT NULL DEFAULT 0, PRIMARY KEY (
`id`) made by include('phar:///usr/local/bin/wp/php/boot-phar.php'), include('ph
ar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php'), WP_CLI\bootstrap,
WP_CLI\Bootstrap\LaunchRunner->process, WP_CLI\Runner->start, WP_CLI\Runner->loa
d_wordpress, require('wp-settings.php'), do_action('init'), WP_Hook->do_action,
WP_Hook->apply_filters, MainWP\Extensions\Domain_Monitor\MainWP_Domain_Monitor_A
dmin->init, MainWP\Extensions\Domain_Monitor\MainWP_Domain_Monitor_DB->init, Mai
nWP\Extensions\Domain_Monitor\MainWP_Domain_Monitor_DB->install, dbDelta
.at domains (Austria) also display a wrong date, namely December 31, 1969.
Not sure why but just tested with a bunch of .eu and .nl domains and non work. They all show incorrect expiry dates and most also show incorrect creation and updated dates.
Any advice would be helpful (already installed the lastest beta
Hi, this extension (version 4.0) does not work for Spanish “.es” domains.
All of the .es domains are reported as expired (red background) for “-19055 days” regardless of the real expiration date, that is different for every one.
Most of the domains I manage are “.es”, so this extension is not useful for me at this point…
Please have a look at this, thanks!
This extension seems to have moved out of beta?
I’m only seeing a complete return for anything .com - all other tld’s are returning incomplete information.
also,
The extension is generating this error about every 3 seconds:
WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘PRIMARY KEY (id)’ at line 1 for query ALTER TABLE ipv_mainwp_domain_monitor CHANGE COLUMN last_check last_check int(11) NOT NULL DEFAULT 0, PRIMARY KEY (id) made by require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), WP_Hook->do_action, WP_Hook->apply_filters, MainWP\Extensions\Domain_Monitor\MainWP_Domain_Monitor_Admin->init, MainWP\Extensions\Domain_Monitor\MainWP_Domain_Monitor_DB->init, MainWP\Extensions\Domain_Monitor\MainWP_Domain_Monitor_DB->install, dbDelta
2 Likes
.PH (for the Philippines) and other variations (.com.ph, .org.ph, etc) aren’t scanned properly.
You may try whois.dot.ph (although they seem to not allow automated searches) and godaddy.com/en-ph/whois.
We are still searching for a solution for country-based domains.
As soon as we find WHOIS servers available, we will include.
2 Likes
Probably, whois.denic.de is blocking automated searches.
Yes, I fear you’re right.
.com is working correctly for me but all UK domains are showing incorrect details (dates all showing as Jan 1 1970) it is picking up the correct registrars though.
1 Like
Hi,
domains “.it” return incorrect data (expiration 1 january 1970)
I’ve also this error log:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘PRIMARY KEY (id)’ at line 1]
ALTER TABLE wp_mainwp_domain_monitor CHANGE COLUMN last_check last_check int(11) NOT NULL DEFAULT 0, PRIMARY KEY (id)
Thank you!
I guess you have to implement some sort of functionality (whitelist/blacklist) for domains that do not display an “Registry Expiry Date”.
It seems that the WHOIS query of .at domains doesn’t include such an expiry date. It at least does not have it when I query .at domains with the whois Linux command. And I also don’t see such a date when using the official registry website at nic.at. Only the “changed” date is displayed.
Some feature tweaks here…
I have several sites that are on a sub domain with the same domain name.
While listing them separately on the Domain Monitor page makes sense I think if you do check the domain for 1 they should all update since they are the same domain.
Also the email message sent out notifying you of the upcoming expiry for each monitor should list all websites on sub domains using the domain, instead of having each monitored sending out their own email (I am talking about those sites on sub domains using the same domain name).
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.