Date format for this server:
Registrar Registration Expiration Date: 2015-01-11T23:00:00-07:00Z

Out for script:

date: invalid date `2015-01-11T23:00:00-07:00Z'
date: invalid date `2015-01-11T23:00:00-07:00Z'
CRITICAL - Domain example.li expired on 2015-01-11T23:00:00-07:00Z

BSD's 'date' command wants different parameters to convert expiration to seconds.

intead of: date +%s --date="$expiration"

we need: date -j -f %F $expiration +%s

I'm using FreeBSD 10.1-RELEASE; but I assume the problem is common amongst freebsd, netbsd, openbsd and OSX (haven't tested).

Sorry not to have written an elegant test to submit. I just hard coded the changes.

-d findtonight.me -w 30 -c 10

date: incorrect date «--Date:»

It seems whois returns error code = 1 with .com domain.

I just change this line (233)

[ $error -eq 0 ] || die "$STATE_UNKNOWN" "UNKNOWN - WHOIS exited with error $error."

By this line

[ $error -eq 0 ] || [ $error -eq 1] || die "$STATE_UNKNOWN" "UNKNOWN - WHOIS exited with error $error."

Then your parsing is ok.

I don't know if whois generates error 1 for other reasons. But for now on, I had no specific problem.

[EDIT] I'm on CentOS7 (with Centreon) and can't use latest whois version :/

The script just stopped working today and spit out invalid date format.

./check_domain -d google.com

date: invalid date ` 14-sep-2020\n 2020-09-13T21:00:00-0700'
date: invalid date ` 14-sep-2020\n 2020-09-13T21:00:00-0700'
CRITICAL - Domain google.com expired on  14-sep-2020
 2020-09-13T21:00:00-0700

Hello:
I'm getting this exit

CRITICAL - Domain domain expired 662751 days ago (0201-12-10). | domain_days_until_expiry=-662751;30;7

with this whois exit:

created:     20141210 #13644956
expires:     20161210
changed:     20141210

thanks in advance
Nomar

We're having an issue running this on BSD (not withstanding the issue reported in #44

Not sure whether it's a BSD vs Linux awk, but some whois servers (whois.nic.uk) are returning carriage returns which are not being removed (and maybe the BSD date formatting is more sensitive to.

I can give examples, but it should be obvious that the following fix would be a useful addition to make parsing a bit more robust:

@@ -452,12 +452,12 @@ else
 	outfile=$(tempfile)
 	run_whois
 fi
-expiration=$(get_expiration $outfile)
+expiration=$(get_expiration $outfile | sed -E 's/[[:space:]]+//g')
 
 [ -   z "$expiration" ] && die "$STATE_UNKNOWN" "UNKNOWN - Unable to figure out expiration date for $domain Domain."

Nagios Core 4.4.2
Works correct:
/usr/local/nagios/libexec/check_domain.sh -d xxx.com --cache-dir /var/cache/check_domain --cache-age 1

No work:
define command{
command_name check_domain_expire
command_line $USER1$/check_domain.sh -d $ARG1$ -w $ARG2$ -c $ARG3$ -C /var/cache/check_domain/ -a 1
}

define service {
use xxx-service-mail-sms
host_name xxx
service_description xxx.com/expire
check_command check_domain_expire!xxx.com!30!7
max_check_attempts 3
notifications_enabled 1
normal_check_interval 720
notification_interval 1440
}

OUTPUT:
UNKNOWN - Domain xxx.com doesn't exist or no WHOIS server available.

Attempting to run check_domain.sh -d example.com (where example.com is a 1and1 domain) results in:

UNKNOWN - WHOIS exited with error 1.

The output for the whois is:

Domain Name: EXAMPLE.COM
Registry Domain ID: 1234567890_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.1and1.com
Registrar URL: http://registrar.1and1.info
Updated Date: 2017-10-01T13:08:01Z
Creation Date: 2017-05-01T13:08:37Z
Registry Expiry Date: 2018-05-01T13:00:00Z
Registrar: 1&1 Internet SE
Registrar IANA ID: 83
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.6105601459
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS-1234.AWSDNS-00.ORG
Name Server: NS-123.AWSDNS-00.COM
Name Server: NS-1234.AWSDNS-00.CO.UK
Name Server: NS-123.AWSDNS-00.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/

Last update of whois database: 2017-10-01T14:00:00Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

I hope that's helpful. It'd be great to get the script working for this as well.

Even if the domain exist, they still get these UNKNOWN errors.

Example of domains:

• godaddy.com
• aframe.com
• google.com

When I add domains to nagios for first interval check time its working correctly and second check internal it goes to unknown state like unable to figure out . I attached screen shot please look it

Occasionally when running a whois the command gets the output we need (with the expiration date, etc.), but a separate part of the request the whois server queried gets denied with the error "fgets: Connection reset by peer"

This means we get our info, but because an error is thrown this line in check_domain.sh means we exit with error 2 instead of continuing to parse the data:

[ $error -eq 0 ] || die "$STATE_UNKNOWN" "UNKNOWN - WHOIS exited with error $error."

Hello,

The script do not recongnize the format "DD/MM/YYYY"

[root@s18252688 nagios-plugin-check_domain]# whois vbrpleugueneuc.fr | grep Expiry
Expiry Date: 04/03/2016

[root@s18252688 nagios-plugin-check_domain]# ./check_domain.sh -d vbrpleugueneuc.fr
UNKNOWN - Unable to figure out expiration date for vbrpleugueneuc.fr Domain.

I edited check_domain.sh adding:

Expiry Date: 19/11/2015

/Expiry Date:/ && $NF ~ DATE_DD_MM_YYYY_SLASH {split($3, a, "/"); printf("%s-%s-%s", a[3], a[2], a[1]); exit}

and now it works.

[root@s18252688 nagios-plugin-check_domain]# ./check_domain.sh -d vbrpleugueneuc.fr
OK - Domain vbrpleugueneuc.fr will expire in 331 days (2016-03-04).

Thanks to update check_domain.sh

Regards
supergyver

Can you please check it and fix it?
UNKNOWN - WHOIS exited with error 1.

TL:DR - Is it worth putting whois package install instructions in when it's quick and easy to Google?

Early in 2014 I rented a fresh CentOS 6 machine and it did not come with the 'whois' installed. It was easy to look up how to do this, but is it worthwhile to put this type of info into README.md?

Normally I just put something like this in my plugins, but it's just an example:

This plugin uses the "whois" command. It is usually installed by default, but if not, you can get it via your favourite package manager:
Debian/Ubuntu: apt-get install whois
RHEL/CentOS: yum install jwhois

If this makes sense, I can create a PR, but I wanted to ask first.

check_domain -d panel.li -w 60 -c 30 -s whois.name.com
check_domain: 29: local: panel.li: bad variable name

check_domain -d panel.li -s whois.name.com
Ok

Hello,
The expiration date for .bg domains does not get extracted by awk script. Whois returns something like:

DOMAIN NAME: alabala.bg

requested on: 03/11/2012 14:12:30.469901 EET

processed from: 21/05/2012 14:31:30.070302 EEST

activated on: 26/05/2012 12:47:39.913045 EEST

expires at: 21/05/2017 00:00:00 EEST

registration status: Registered

Here's what needs to be done:

 check_domain.sh | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/check_domain.sh b/check_domain.sh
index 201e98c..70bd912 100755
--- a/check_domain.sh
+++ b/check_domain.sh
@@ -146,6 +146,8 @@ expiration=$(
        DATE_DD_MON_YYYY_HHMMSS_TZ = "[0-9][0-9]-" MON "-" YYYY " " HH_MM_DD " UTC"
        #2016.01.14 18:47:31
        DATE_YYYYMMDD_HHMMSS = DATE_YYYY_MM_DD_DOT " " HH_MM_DD
+       # 21/05/2017 00:00:00 EEST
+       DATE_DD_MM_YYYY_SLASH_HHMMSS_TZ = DATE_DD_MM_YYYY_SLASH " " HH_MM_DD " [A-Z]+"

        split("january february march april may june july august september october november december", months, " ");
        for (i in months) {
@@ -247,6 +249,9 @@ expiration=$(

    # [State] Connected (2014/12/01)
    /\[State\]/ && $NF ~ DATE_YYYY_MM_DD_SLASH {gsub("[()]", "", $3); split($3, a, "/"); printf("%s-%s-%s", a[1], a[2], a[3]); exit}
+
+   # expires at: 21/05/2017 00:00:00 EEST
+   $0 ~ "expires at: *" DATE_DD_MM_YYYY_SLASH_HHMMSS_TZ {split($3, a, "/"); printf("%s-%s-%s", a[3], a[2], a[1]); exit}
 ' $outfile)

 [ -z "$expiration" ] && die "$STATE_UNKNOWN" "UNKNOWN - Unable to figure out expiration date for $domain Domain."

Please consider this for the next release.

Thanks,
Borislav Ivanov

/usr/local/nagios/libexec/check_domain.sh -w 30 -c 10 -d stuff.co.nz

UNKNOWN - Unable to figure out expiration date for stuff.co.nz Domain.

/usr/local/nagios/libexec/check_domain.sh -w 30 -c 10 -d trademe.co.nz

UNKNOWN - Unable to figure out expiration date for trademe.co.nz Domain.

/usr/local/nagios/libexec/check_domain.sh -w 30 -c 10 -d pricespy.co.nz

UNKNOWN - Unable to figure out expiration date for pricespy.co.nz Domain.

no problem when run on check_domain.sh
[librenms@localhost plugins]$ ./check_domain.sh -d google.com
OK - Domain google.com will expire in 425 days (2020-09-13). | domain_days_until_expiry=425;30;7

however ./check-services.php not work
Nagios Service - 4
Request: '/usr/lib64/nagios/plugins/check_domain.sh' '-H' 'GOOGLE.COM' '-d'
check_domain.sh: invalid option -- 'H'
check_domain.sh: option requires an argument -- 'd'
Perf Data - None.
Response:
./check-services.php 2019-07-15 17:45:32 - 2 services polled in 0.385 secs

thanks for help

Hi experts,
I'm using script check_domain.sh to check expiry domain .vn, but always return error UNKNOWN - WHOIS exited with error 1.

Would you be able to add for autoproff.pt domain

whois autoproff.pt
[Querying whois.dns.pt]
[whois.dns.pt]
Nome de domínio / Domain Name: autoproff.pt
Data de registo / Creation Date (dd/mm/yyyy): 19/01/2015
Data de expiração / Expiration Date (dd/mm/yyyy): 18/01/2016
Estado / Status: ACTIVE

Titular / Registrant
XXXXXXX
XXXXXXX
XXXXXXX
Email: XXXXXXX

Entidade Gestora / Billing Contact
EPAG Domainservices GmbH
Email: XXXXXXX

Responsável Técnico / Tech Contact
EPAG Domainservices GmbH
Email: XXXXXXX

Nameserver Information
Nameserver: autoproff.pt NS ns4.gratisdns.dk.
Nameserver: autoproff.pt NS ns1.gratisdns.dk.
Nameserver: autoproff.pt NS ns2.gratisdns.dk.
Nameserver: autoproff.pt NS ns5.gratisdns.dk.
Nameserver: autoproff.pt NS ns3.gratisdns.dk.

This one also include expiry date information (Data de expiração / Expiration Date (dd/mm/yyyy): 18/01/2016). Thanks

example: whosi ovh.com

Domains registered there are using another syntax:
Registry Expiry Date: 2025-02-08T05:00:00Z

Can You add it to the script?

Thanks a lot!

Would it be possible to add support for LibreNMS?

In LibreNMS a script called check_services.php calls the required "check" script. It always passes -H hostname.example.com. But when it calls the check_domain script it fails and returns an error check_domain.sh: invalid option -- 'H'.

The check_domain.sh script works correctly if I call it manually from the command line
./check_domain.sh -d google.ca -C /tmp -a 1
OK - Domain google.ca will expire in 63 days (2019-04-28). | domain_days_until_expiry=63;30;7

Would it be possible to have the check_domain.sh script updated to ignore the -H hostname.example.com so that it won't return an error?

Hello Elan and fellow users,

I would like to discuss appending performance data, changing the output from this:

$ ./check_domain.sh -d github.com -w 30 -c 10
OK - Domain github.com will expire in 2056 days (2020-10-09).

to something like this:

$ ./check_domain.sh -d github.com -w 30 -c 10
OK - Domain github.com will expire in 2056 days (2020-10-09).|days=2056;30;10;0;

This would move the plugin from Case 1 to Case 2 as defined by the Nagios Plugin API and uses the format:

|varname=value;warning;critical;min;max

Some options for implementation could be:

• Adding a new command line option set (for example: "-p|--perfdata")
  • Might be confused with -P, so -f or something else might be better?
• Making it the default for the current script
  • If this doesn't break any current usage, it would enhance the plugin by adding graphs to systems like Check_MK that utilize performance data automatically.
• Adding a new script that appends the performance data as the default
  • Avoids issues above, but wastes space & effort.

As none of the above seem non-trivial, I figured it would be best to discuss this with you and the community before I went too far down any of these roads, since I would hope to eventually have the code mainlined.

Thanks for making this great plugin!

[root@lenovo ~]# ./test.sh wolliz.de
-> wolliz.de
UNKNOWN - Unable to figure out expiration date for wolliz.de Domain.
<- wolliz.de
[root@lenovo ~]#

Hi @glensc & @PasiJarnstedt
I want to know the expiry date of .au and .eu domains , unable to get them from this script (error:UNKNOWN - Unable to figure out expiration date for *****.eu domain) need to add different servers for those requests i think , as i have zero knowledge in scripting so could you please provide me the updated script , so that it will be very helpful to me. And for .ie domains it is not working all the time some time it is giving error like unable to figure out expiry and some time it is providing expiry date.
Thanks in advance

I'm trying to test the domain test, but get an error:
./check_domain.sh -d vk.com
UNKNOWN - WHOIS exited with error 1.

Hi,

it does not work for the below domains.
autoproff.ir expire-date: 2016-02-05 (expiry date format from the "whois somedomain.ir" command)
autoproff.pl renewal date: 2016.01.14 18:47:31
autoproff.pt Data de expiração / Expiration Date (dd/mm/yyyy): 18/01/2016
autoproff.si expire: 2016-01-19
autoproff.at
autoproff.be
autoproff.ch
autoproff.de
autoproff.es
autoproff.eu
autoproff.fr
autoproff.gl
autoproff.gr
autoproff.li
autoproff.lt
autoproff.lu
autoproff.lv
autoproff.nl

Most of these domains are purchased by us but not used for hosting yet.

The response I get for all is below.
UNKNOWN 02-16-2015 01:25:02 0d 0h 21m 43s 3/3 UNKNOWN - Unable to figure out expiration date for somedomain.eu Domain.

If possible please make the changes to accommodate above root domains.

Hi,

Kindly add support for .com.cn and .cn tlds. Expiration date format is given below for the 2 domains.

[root@monitor ~]#whois gogovcard.com.cn
[Querying whois.cnnic.cn]
[whois.cnnic.cn]
Domain Name: gogovcard.com.cn
ROID: 20150218s10011s84514959-cn
Domain Status: clientTransferProhibited
Registrant ID: p44023925
Registrant: MARCARIA NETWORK LTD
Registrant Contact Email: [email protected]
Sponsoring Registrar: 广ä¸æ¶ä»£äºèç§ææéå
¬å¸
Name Server: ns01.trademarkarea.com
Name Server: ns02.trademarkarea.com
Registration Time: 2015-02-18 05:14:08
Expiration Time: 2016-02-18 05:14:08
DNSSEC: unsigned

[root@monitor ~]# whois gogovcard.cn
[Querying whois.cnnic.cn]
[whois.cnnic.cn]
Domain Name: gogovcard.cn
ROID: 20150218s10001s73956434-cn
Domain Status: clientTransferProhibited
Registrant ID: p44023925
Registrant: MARCARIA NETWORK LTD
Registrant Contact Email: [email protected]
Sponsoring Registrar: 广ä¸æ¶ä»£äºèç§ææéå
¬å¸
Name Server: ns01.trademarkarea.com
Name Server: ns02.trademarkarea.com
Registration Time: 2015-02-18 05:14:09
Expiration Time: 2016-02-18 05:14:09
DNSSEC: unsigned

./check_domain.sh -d yandex.ru
date: invalid date `2018-09-30T21:00:00Z'

This comment solve problem:

https://exchange.nagios.org/directory/Plugins/Internet-Domains-and-WHOIS/check_domain/details#rev-4119

(Tested on DigitalOcean droplets with Ubuntu 14.04 x64, Debian 7.2 x64, CentOS 7.2 x64, and CentOS 6.7 x64.)

When I run the following command on Debian-based distributions...
./check_domain.sh -d fakedomainaaa.com
...the output is...
UNKNOWN - WHOIS exited with error 1.

This doesn't happen on either of the CentOS servers I tried it on.

Domains that do exist have no issues.

phonedot.mobi

Hey Elan, as you know I'm not that strong of a coder, but I get by (barely). For a few years I've occasionally used the shellcheck.net website to verify that my code is good for shell scripts.

I ran check_domain.sh through it and there were a few issues it found. Nothing major, of course.

Would you find it valuable if I went through the results and submitted a PR with an updated version with help from that site?

Thank you @oasys for updating the script to make rate limited responses unknown again as opposed to critical in #28, that helped a lot!

My issue is that I'm checking over 100 domains for my clients and most of my clients have .org addresses so I've been coming up against the domain limiting for years.

Has anyone figured out a way to completely avoid it either in the plugin code or in nagios/icinga settings?

I use Icinga 1.11.6, and I've tried telling Icinga to allow more failures, check only twice per 24 hours, max_service_check_spread set to 180 minutes to spread out initial checks, and still pir.org's rate limiting logic stymies me.

Thanks in advance.

I was able to do the following to get expiration date on .io domains, but since it's a popular one, can you have the lookup host build into the script?

./check_domain.sh -s whois.nic.io -d zeeto.io

One of my friends had their domain registered by somebody else long ago and now it's expired and they can't get control of it to renew. The domain has status "redemptionPeriod http://www.icann.org/epp#redemptionPeriod". They want me to wait until it's deleted and snatch it up so they continue using it. I looked up the registrar and I know the values for approximately when it's going to be released/deleted.

I have two options:

1. I can create a little plugin to monitor the "status" of the domain and notify me when it enters or exits a specific status, or...
2. I could use this plugin but use negative values for $warning and $critical

I've created a branch with the modified logic. I'll create a pull request so you can take a look.

Also, let me know if you think that this functionality doesn't really fit with what this plugin is meant to do. I'm not entirely sure myself. 😸

Hi!.

The Script does not work properly with .com Domains

bash /usr/local/nagios/libexec/check_domain.sh -d  githubusercontent.com
UNKNOWN - WHOIS exited with error 1.

bash /usr/local/nagios/libexec/check_domain.sh -d  freetsa.org          
OK - Domain freetsa.org will expire in 119 days (2017-12-18). | domain_days_until_expiry=119;30;7

whois Version: RIPE Database Query Service version 1.89.2

Regards