On 23.06.18 19:00, Russell Coker via luv-main wrote:

All I want is a way of discovering when my domains will expire which doesn't depend on receiving email from Melbourne IT or similar.

If payment is annual, then isn't it almost sufficient to use "calendar" to email you a month in advance? (I have it reminding me each day for a fortnight before important birthdays, so I have time to buy a card/gift) If there are grounds for paranoia, then maybe run a lookup after 6,9,11 months, as back-up? Three per year shouldn't trigger much aggression? Finding out after expiry is the bit that I don't understand. (OK, I've just added car rego to ~/.calendar/calendar, as I'm liable if Vicroads forget to send me a bill.) Note: The file is like a makefile - don't let tabs be converted to spaces. (I use a vim modeline for that.) Fortnight lookahead: -l 14 Erik

I wrote:

To this day, every Sunday I get e-mail via a cron job that runs domain-check against a set of about three dozen domains (mine, friends', and those of institutions I care about) to tell me which of them are within 90 days of expiration (and if any are past expiration).

FYI, here's an example report sent using said cron job, that leverages Ben Okopnik's 'domain-check' Perl script: ---<begin>--- Date: Sun, 24 Dec 2017 07:12:02 -0800

From root@linuxmafia.com Sun Dec 24 07: 2:02 2017 From: root <root@linuxmafia.com> To: rick@linuxmafia.com Subject: domain-check: Domain expiration warning (90 day cutoff)

According to 'whois', these domains will expire soon: pentaclemoon.com (in 16 days) electriclichen.com (in 20 days) berkeleylug.com (in 26 days) animelosangeles.com (in 26 days) chicon.org (in 30 days) grrattitude.com (in 33 days) computerhistory.org (in 39 days) maruch.org (in 43 days) spinster.org (in 44 days) lugod.org (in 44 days) wsfa.org (in 45 days) badens.org (in 47 days) linuxdojo.net (in 60 days) chair-in-the-sky.com (in 65 days) cain.org (in 65 days) svlug.net (in 71 days) nblug.org (in 72 days) landley.net (in 77 days) zwilnik.net (in 82 days) nesfa.org (in 83 days) mib.org (in 86 days) whensday.info (in 88 days) likkitownsend.com (in 90 days) desamojones.com (in 90 days) ---<end>--- That mail was generated by my local /etc/cron.weekly/domain-check cron job, which is as follows: ---<begin>--- #! /bin/sh # domain-check Cron script to check domain expirations. # # This is a pitifully primitive cron script to invoke domain-check # by Ben Okopnik ( ben@linuxgazette.net ) against lists # of domains in /usr/local/share. A better replacement # would notify a list of appropriate persons for each # domain, rather than just Rick Moen. # # Written by Rick Moen (rick@linuxmafia.com) # $Id: cron.weekly,v 1.01 2007/07/02 21:03:05 rick set -o errexit #aka "set -e": exit if any line returns non-true value set -o nounset #aka "set -u": exit upon finding an uninitialised variable test -e /usr/local/share/domains || exit 0 test -x /usr/local/bin/domain-check || exit 0 /usr/local/bin/domain-check -w -e=rick@linuxmafia.com -x=90 -F=/usr/local/share/domains ---<end>--- My /usr/local/share/domains file is simply an ASCII list of domains I wish to be periodically checked, listed one per line.

Quoting Anthony (anthony-luv@hogan.id.au):

Australian domain whois also doesn't show expiry info.

Quite. This astonishing-to-me-in-2007 fact is highlighted prominently in my referenced _Linux Gazette_ article. The domain I tested, as revealed in the article, was, in fact, luv.asn.au. (That revelation means that all three implementations of the checking script are useless for .au domains, sadly. Fortunately, even for hosts in Oz, .au is not the only possible TLD. For hosts where that DNS constraint applies, true, other solutions would be required.)

Unfortunately you can't poll whois for a .au domain more than 20 times a day from the same IP.

FWIW, Ben Okopnik's (and, IIRC, Jesse Monroy's) Perl code includes rate-limiting code for some _other_ TLDs that are punitive of frequent queries, albeit not quite that punitive.

Quoting Anthony (anthony-luv@hogan.id.au):

The Aus approach was indeed taken due to spam considerations, trying to limit data mining of whois records (the daily rate limiting), and renewal scams based upon listed expiry dates (I remember reading through auDA doco as it came into being after Melbourne IT lost the exclusive gig).

Yes, after initially being astonished at the withholding of expiry dates in .au domain WHOIS, I read about the rationale, and one must of course acknowledge that it makes sense. FWIW, I offered Ben's and Jesse's domain-check scripts as candidate solutions for Russell's problem because he said merely that he was seeking a tool to monitor expiration status for _domains_. The stated context wasn't specifically _.au_ ones -- but, note, I also made sure to highlight the _Linux Gazette_ article to highlight the .au roadblock so Russell wouldn't be surprised. All GTLDs (I think) and _almost_ all country-code TLDs (ccTLD) domains' data parse fine. (I think.) ICANN keeps creating weird and obscure GTLDs, though, which is one reason why any tool like Ben's and Jesse's needs occasional maintenance. And the _other_ reason is that even long-established TLDs sometimes change their WHOIS date reporting in ways that break parsing, for no good reason. To craft a monitoring tool for .au domains, I believe one would need to write code to login to registrar records as the owner, and parse the expiry data there. Which _could_ work. Or: https://stackoverflow.com/questions/1732348/regex-match-open-tags-except-xht... ;->

Back on track... I think we're seeing the eventual death of WHOIS, due to GDPR.

Interesting point. WHOIS service, and most particularly classic 43/tcp WHOIS service, has been the red-headed stepchild for decades for other reasons, too. For one thing, the current breed of desktop users almost never even think to use it. MS-Windows doesn't come with a client, and MacOS X has only a Unix-standard console client, so Macheads typically never notice it. And, as with the main reason why Gopher was supplanted by the Web, port-43 WHOIS service is text-bound and non-advertising-friendly. Quite a few ccTLDs offer WHOIS only via Web front-ends, partly in consequence. And now, as you say, argubly there's Yet Another GDPR Objection to deal with. I fear you're right.

Hopefully there'll at least be a system that provides base info:

One can conceive of a standard authenticated-owner interface to permit domain principals to look up such data, sidestepping EU privacy objections. Maybe. But of course, public ability to check _other_ people's domain details, relied on by Ben and Jesse's tools and frankly by many people all the time, suffers. E.g., I can't tell you how many times I've tried to help an acquaintance with, say, his/her domain about to expire, and the e-mail addresses on record were utterly useless but the names and telephone numbers of the Registrant, Administrative Contact, and Technical Contact were crucial. The 'e-mail addresses prove useless for an unexpectedly expiring domain' syndrome is predictable, if you think about it: If the listed contact e-mails had been an effective means of reaching the key people, they wouldn't have ignored about five or six consecutive renewal notices.

Quoting Bradley@NorthTech.US (Bradley@NorthTech.US):

As an admin I can't say that I concur in the least - especially when there is the choice of proxies in the form of privacy bureaus.

You'll note I didn't say I agreed with the policy, just that the rationale made sense. (I expect my overall view ought to be clear given that I've been trying for over a decade to promote and maintain software tools that rely on public WHOIS data.)