Monitoring
Domain monitoring
Understand registration dates, missing expiry information, partial data, and temporary registry failures.
Domain monitoring checks registration information for the Website’s registrable domain when the registry makes that information available. Not every registry publishes an expiry date.
What you may see
Open a Website and select Domain to see the latest registration result and observation time. Depending on the registry, PingAgain may show important dates, registration status, registrar information, or only some of those details.
Understand the result
- Expiry date available — the registry returned a date PingAgain can display.
- Expiry not provided — the lookup succeeded, but the registry did not publish an expiry date.
- Partial registry information — some useful registration fields are available, but the response is incomplete.
- Registration information unavailable — no suitable registration-data service is available for this domain ending.
- Temporary provider failure — the registry service could not answer reliably; PingAgain keeps the failure state and retries later.
PingAgain does not invent an expiry date or report success when the provider did not return trustworthy data.
Temporary lookup failures
Check the observation time and try again later. Do not recreate the Website: that does not make the external registry available. Contact support if the same domain remains unavailable across repeated scheduled attempts while other Domain monitors work normally.
Technical details
PingAgain uses RDAP, the modern registration-data service, to find the responsible registry. Routes come from the IANA registry directory over HTTPS rather than from a fixed list inside PingAgain, so newly published routes can become available through a safe directory refresh.
Public Suffix List rules identify the registrable domain correctly for multi-level endings such as co.uk and com.au. Internationalized names are handled in their standard ASCII form when PingAgain contacts the registry. A registry may still omit fields, reject a request temporarily, or have no RDAP route; the result shown in PingAgain reflects that outcome.
Next: see monitoring troubleshooting or learn how partial results are shown.