.PAY domain
Already registered
Looks like HeyLight, a likely payments/checkout brand name rather than a generic term. In .PAY priority land, that would fit a trademarked fintech or embedded-payments product if the mark is valid.
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.
Start at domain.pay, search the label, then choose the right path: trademark fast-track if you qualify, or pre-order for a first-day attempt when broader access opens. Use this page: https://domain.pay/register. Registration is subject to registry rules and availability.
DNS lets you split services: MX records on heylight.pay route mail to your mailbox host while A/CNAME records send web traffic to a separate web host. They operate independently, so heylight.pay can use one vendor for email and another for the site. Just keep each record set correct.
Yes. If you do not have a matching trademark, use domain.pay to pre-order a first-day registration attempt for broader availability: https://domain.pay/register. A pre-order is not a guarantee; the name may become unavailable, premium, reserved or blocked before submission.
Stand up the new site on heylight.pay at a low TTL, validate it on a staging hostname, then flip DNS and 301 every old URL to its match on heylight.pay. Submit a change of address in Search Console and keep the old certificate valid through the cutover. Monitor heylight.pay for crawl errors afterward.
Yes. A wallet or payment app can use .PAY for a memorable payment-specific entry point. Check candidate labels through domain.pay: https://domain.pay/domains. If you own a matching trademark, consider the priority route; otherwise pre-order for broader access.
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.