| Domain Name | Status | Delete | Reg. | Age | History | Captures | Rank | RD | D | TLD | Actions | # |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| lexiang.press | pending delete | 2016 | — | 0 | — | — | — | — | 1 | |||
| btcinfo.press | pending delete | 2025 | 0 | 3 | — | — | — | — | 2 | |||
| daginfo.press | pending delete | 2025 | — | 0 | — | — | — | — | 3 | |||
| daginform.press | pending delete | 2025 | — | 0 | 0.26 | 1 | — | — | 4 | |||
| tiktokvip.press | pending delete | 2025 | — | 0 | — | — | — | — | 5 | |||
| medspa.press | pending delete | 2024 | 2 | 5 | — | — | — | — | 6 | |||
| stockexchange.press | pending delete | 2019 | 8 | 8 | — | — | — | — | 7 | |||
| kelpdaos.press | pending delete | 2025 | — | 0 | — | — | — | — | 8 | |||
| zengos.press | pending delete | 2025 | 0 | 2 | — | — | — | — | 9 | |||
| promfeed.press | pending delete | 2025 | — | 0 | — | — | — | — | 10 | |||
| promteamannouncement.press | pending delete | 2025 | — | 0 | — | — | — | — | 11 | |||
| dacia.press | pending delete | 2025 | 3 | 57 | 0.89 | 4 | — | — | 12 | |||
| progressnews.press | pending delete | 2025 | 6 | 73 | — | — | — | — | 13 | |||
| natureidea.press | pending delete | 2025 | — | 0 | — | — | — | — | 14 | |||
| emit.press | available | 2024 | 2 | 5 | — | — | — | — | 15 | |||
| informer.press | available | 2024 | 8 | 24 | 0.42 | 1 | — | — | 16 | |||
| moto.press | available | 2014 | 8 | 9 | 0.60 | 1 | — | — | 17 | |||
| izlaz.press | available | 2025 | — | 0 | — | — | — | — | 18 | |||
| floppy.press | available | 2024 | 2 | 15 | — | — | — | — | 19 | |||
| phir.press | available | 2025 | — | 0 | — | — | — | — | 20 |
Take this list with you: this day as a CSV file · RSS feed · domain name lists
How this works: the registry publishes a zone file once a day listing every domain with nameservers. We compare each day's file with the previous one; a name that disappears has almost always been deleted and enters a 30-day redemption period, followed by five days of pending delete, after which it is released. We confirm every name with the registry's RDAP service before it is listed as a drop. After the drop a name is released or registered again: the day's batch is seen go on a sample of the registry's names, and a caught name shows up in the next day's zone file.