| Domain Name | Status | Delete | Reg. | Age | History | Captures | Rank | RD | D | TLD | Actions | # |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| swankys.cafe | pending delete | 2023 | 2 | 2 | — | — | — | — | 1 | |||
| nestlecoffeetasty.cafe | pending delete | 2025 | — | 0 | — | — | — | — | 2 | |||
| batoh.cafe | pending delete | 2024 | 2 | 2 | — | — | — | — | 3 | |||
| bollywood.cafe | pending delete | 2015 | 8 | 4 | — | — | — | — | 4 | |||
| floresta.cafe | pending delete | 2025 | — | 0 | — | — | — | — | 5 | |||
| deanlewis.cafe | pending delete | 2024 | 2 | 13 | — | — | — | — | 6 | |||
| coffeeteaplusme.cafe | pending delete | 2025 | — | 0 | — | — | — | — | 7 | |||
| snack.cafe | pending delete | 2023 | 3 | 10 | 0.15 | 1 | — | — | 8 | |||
| besuchs.cafe | released — checking | 2023 | 1 | 1 | — | — | — | — | 9 | |||
| oldquarter.cafe | available | 2024 | 2 | 5 | — | — | — | — | 10 | |||
| pinkpanther.cafe | available | 2025 | — | 0 | — | — | — | — | 11 | |||
| 100n.cafe | available | 2024 | 4 | 12 | 1.09 | 11 | — | — | 12 | |||
| fursome.cafe | available | 2023 | 2 | 15 | — | — | — | — | 13 | |||
| mayan.cafe | available | 2024 | 2 | 4 | — | — | — | — | 14 | |||
| 78win.cafe | available | 2023 | 2 | 28 | 1.11 | 2 | — | — | 15 | |||
| piro.cafe | available | 2025 | — | 0 | — | — | — | — | 16 |
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.