.PAY domain
Already registered
Looks like Apoliva, a trademark-style name used by a beauty/skincare brand in several markets. In a priority-window .PAY registration, that makes the strongest fit a brand owner, though the exact registrant can’t be confirmed.
Data sourced live from the .PAY registry's RDAP server (Nominet). Cached by domain.pay; refreshed in the background when older than the configured TTL.
Broader .PAY access is tied to the post-LRP period around February 2027, subject to registry and registrar confirmation. If you do not have a trademark, use domain.pay to pre-order a first-day attempt: https://domain.pay/register.
Export the full zone file for apoliva.pay from your DNS host, or record each record set, so you can restore quickly after a mistake or provider change. Keep the backup of apoliva.pay's zone versioned and off the provider. Re-import it to rebuild apoliva.pay if the zone is ever lost.
A marketplace can use .PAY for seller payouts, buyer checkout, escrow, billing or payment support flows. Generate and verify names through domain.pay: https://domain.pay/domains. Choose a label that customers will recognize as official and safe.
To switch DNS hosts for apoliva.pay, recreate your existing records at the new provider first, then update the nameservers for apoliva.pay at the registrar to the new ones. Keeping the zone identical avoids downtime during the cutover. Edit nameservers for apoliva.pay from /domains.
settle.pay may be a useful .PAY direction if it matches your brand and payment journey, but availability is not guaranteed. Check and pre-order through domain.pay: https://domain.pay/domains. Prefer simple labels that customers can remember and trust.
Availability is checked live and re-verified before payment. Pre-orders are first-day registration attempts — registration is not guaranteed; 100% credit toward another domain (or 80% cash refund) if unsuccessful.