pypolicyd_spf reference to URL openspf.net?

I've got

 pypolicyd_spf-2.0.2

installed,

 find /usr/lib/python* -type f -name "*spf*"
  /usr/lib/python3.6/site-packages/spf.py
  /usr/lib/python3.6/site-packages/policydspfuser.py
  /usr/lib/python3.6/site-packages/pypolicyd_spf-2.0.2-py3.6.egg-info
  /usr/lib/python3.6/site-packages/__pycache__/policydspfuser.cpython-36.pyc
  /usr/lib/python3.6/site-packages/__pycache__/policydspfsupp.cpython-36.pyc
  /usr/lib/python3.6/site-packages/__pycache__/spf.cpython-36.pyc
  /usr/lib/python3.6/site-packages/policydspfsupp.py

after a recent upgrade to postfix 3.4, checking logs, I noticed

 ...
 Mar 1 11:33:23 mx04 postfix/postscreen-internal/smtpd[5644]: NOQUEUE: reject: RCPT from o10.email.yotpo.com[192.254.121.91]: 550 5.7.24 <email address hidden>: Recipient address rejected: Message rejected due to: SPF Permanent Error: Void lookup limit of 2 exceeded. Please see http://www.openspf.net/Why?s=mfrom;<email address hidden>;ip=192.254.121.91;r=<UNKNOWN>; from=<email address hidden> to=<email address hidden> proto=ESMTP helo=<o10.email.yotpo.com>
 ...

which appears to be an error message generated by

 cat policyd-spf
  ...
  def _rejectmessage(result, type, info, ip, recipient):
      if result[3] == 'reject':
          rejectdefer = "rejected"
      elif result[3] == 'defer':
          rejectdefer = "deferred"
>> url = ("http://www.openspf.net/Why?s={0};id={1};ip={2};r={3}"
                .format(type, info, ip, recipient))
      msg = configData.get('Reason_Message')
      return msg.format(
              rejectdefer=rejectdefer,
              spf=result[1],
              url=url,
      )
  ...

Both openspf.org, and openspf.net appear to be down.

A google search,

 https://www.google.com/search?q=openspf.org+status

pops up one mention
 ...

 OpenSPF's SPF tools
 www.openspf.org/Tools

     Anonymous View

 Nov 9, 2018 ... NOTE: The openspf.net tester is currently out of service. We provide an e-mail based record tester. Send an e-mail to <email address hidden>.
 ...

My logs actually have lots of these messages back thru Dec (as far as I keep 'em). Unclear to me if/when the referred link was actually working.

Is this fixable/fixed with an alternative in pypolicyd_spf-2.0.2 ?
Or is it now time to switch to its apparent successor, spf-engine?