# Domain health and expiration monitoring

Source: https://pingy.io/features/domain-health

Keep the domain behind your website in view.

A healthy web server still depends on a registered domain and a working delegation. Pingy brings registration data, registrar details, expiry, status codes and nameserver evidence into one report. Review risks while the website is still responding, and keep a record of changes.

## Read the registration record

Pingy retrieves registration data through RDAP and identifies the registrable domain behind the hostname. A monitor for www.example.com therefore reports registration information for example.com. Field availability depends on what the registry and registrar publish.

### Registration state

Whether the lookup identifies a registered domain or another response state.

Investigate a missing registration separately from a web server that is offline.

### Expiration and days remaining

The published expiration date and remaining registration period.

Check renewal timing before the domain approaches expiry. Confirm billing and renewal arrangements with your registrar.

### Created and last changed

Published registration and modification dates.

Put a transfer or registration update in context. A modification timestamp does not describe exactly what changed.

### Registrar and IANA ID

The registrar name and identifier when available in the response.

Find the provider responsible for registration changes and distinguish it from your DNS or hosting provider.

### Registry ID and RDAP source

The domain handle and the source of the registration lookup when supplied.

Identify the record being inspected and review the underlying registration authority.

### WHOIS server and abuse contact

Published legacy WHOIS server and registrar abuse contact information.

Keep useful reference details together. A blank field can mean the source did not publish it.

## Check locks, holds and pending changes

Domain status codes describe restrictions and lifecycle states at the registrar or registry. A transfer lock is usually expected for a domain that is staying with its registrar. A hold needs a different response because it can prevent the domain from being published in DNS.

### Transfer protection

Transfer-prohibited status in the published registration record.

Review an unexpected removal of the lock, or confirm an intentional transfer step.

### Delete protection

Delete-prohibited status when published.

See whether deletion restrictions are present alongside transfer protection.

### Registrar and registry holds

Hold status in the returned domain record.

Contact the registrar to resolve the hold; changing a website's A record may not address it.

### Pending actions and lifecycle status

Published transfer, renewal, redemption or deletion-related statuses.

Understand which operation or lifecycle stage needs attention before changing hosting settings.

## Compare registration with live DNS

Registration data and authoritative DNS answer different questions. Pingy puts them together so you can review the nameservers on record alongside the servers that answer for the domain. Reputation signals add another check, with unavailable providers kept distinct from clean results.

### Registry nameservers

Nameservers listed in registration data.

Confirm the delegation recorded after changing DNS providers.

### Nameserver agreement and authority

Consistency with live nameserver data and signs of lame delegation.

Investigate a registration record pointing to servers that do not serve the zone correctly.

### DNSSEC registration signal

Whether registration data reports a signed delegation.

Review the registration side of DNSSEC. Use the DNS report for the live DNSSEC evidence.

### Domain and IP reputation

Available blocklist results for the domain and server address.

Investigate a listing with the named provider. A clean result is limited to the sources queried and is not a universal safety guarantee.

### Domain health grade

A summary across expiry buffer, registrar lock, DNSSEC, nameservers and reputation.

Find areas worth reviewing, then read the evidence. The grade cannot reveal private registrar account settings.

## Before and after a domain transfer

Check the registrar, published expiry date, transfer status and nameservers before starting. An intentional unlock should have a clear owner and a defined transfer window. Keep access to the registrar account and confirm renewal arrangements there.

After the transfer, compare the registrar and nameservers again. Verify that the domain resolves and serves the expected certificate. If a registry field is absent, consult the source or registrar rather than treating a missing value as proof of a fault.

## Scheduled monitoring

Pro and Enterprise audit domain registration daily. Monitoring can alert on approaching expiry, registrar changes, removed transfer protection and new holds. Related DNS monitoring tracks nameserver and DNSSEC changes. A public check provides the available registration snapshot without starting recurring audits.

## Will Pingy renew or transfer the domain for me?

No. Renewal, payment, ownership changes and transfers remain with your registrar. Pingy reports the public evidence and changes it observes.

## Why are some RDAP or WHOIS fields missing?

Registries and registrars publish different fields, and some data may be withheld or unavailable. Pingy labels missing data rather than inventing it. A successful lookup can still have no WHOIS server or contact value.

## Does a registry expiry date prove that auto-renew is enabled?

No. Public registration data does not establish your payment method, account access or registrar auto-renew settings. Check those in the registrar account.

[Domain status codes (ICANN)](https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en)