PD Domain Radar for WHMCS and Blesta

Your domain data is only as good as the day it was entered.

WHMCS or Blesta records an expiry date at registration and a set of nameservers. It has no idea that a customer repointed their DNS last week, that the transfer lock came off, that the registry flagged the name pendingDelete, that ICANN verification was never completed, or that the customer domain you look after but did not register is about to lapse.

All of that is public registry data. PD Domain Radar reads it and tells you what needs attention.

How it works

You import your WHMCS or Blesta domains once, and add any you do not manage but still care about.

The module asks the registry itself — not WHMCS's or Blesta's copy — on a schedule, and raises a finding when something is wrong or about to be: an expiry approaching, a transfer lock off, nameservers changed since last time, DNSSEC dropped. Each finding records when it first appeared, so a new problem stands out from one you already knew about.

Your customer sees nothing. This is your early-warning system, not theirs.

The point is the phone call you never get, because you renewed the domain a fortnight before it lapsed.

Registry truth, over RDAP

RDAP is the structured protocol that replaced free-text WHOIS at gTLD registrars. It returns defined fields instead of a wall of differently-formatted text, which is why this module can say "the transfer lock is off" rather than handing you something to read yourself.

For every domain it collects: registrar, EPP status codes, registration and expiry dates, live nameservers, DNSSEC signing and transfer lock.

Findings, not a data dump

• Expired and expiring soon — with your own warning and critical windows.
• Auto-renew is off close to expiry — the single most common way a domain lapses by accident.
• Nameservers changed — the live delegation no longer matches WHMCS or Blesta. Usually a customer moving their DNS; sometimes the first visible sign of a transfer away.
• Transfer lock off, transfer in progress, pending delete, registry hold.
• Registrant not verified — domains get suspended for this.
• DNSSEC removed — off by default, for hosts who sign their customers' zones.

Each one carries a severity, an explanation in plain language, and the date it first appeared, so a new problem stands out from one you already know about. Accept the ones that are fine and they leave the list without being forgotten — and come back if they change.

Domains that are not in WHMCS or Blesta

Add them to the watchlist: a customer's name held elsewhere, a brand you defend, a domain you are waiting on. They are checked exactly like the rest.

Honest about what it cannot see

Not every extension publishes a registry lookup service, and registries have bad days. When a lookup fails, the module says "could not be checked" — one low-severity note — instead of treating missing data as "unlocked, unsigned, expiring". A monitoring tool that cries wolf is worse than no monitoring tool.

Careful with your registrations

The only change it makes is local: switching WHMCS's or Blesta's own auto-renew flag back on when you ask. Locks, transfers and contacts are deep links into WHMCS or Blesta. It reports; it does not act on your registrations.