21 names match
| Domain Name | Status | Delete | Reg. | Age | History | Captures | Rank | RD | Actions | # |
|---|---|---|---|---|---|---|---|---|---|---|
| hehl.dev | pending delete | 2024 | 1 | 1 | — | — | 1 | |||
| hamdb.dev | pending delete | 2025 | — | 0 | — | — | 2 | |||
| jsonai.dev | pending delete | 2024 | 2 | 4 | — | — | 3 | |||
| keisol.dev | pending delete | 2025 | 1 | 6 | — | — | 4 | |||
| onubio.dev | pending delete | 2025 | — | 0 | — | — | 5 | |||
| dibakar.dev | pending delete | 2025 | — | 0 | — | — | 6 | |||
| jasnoor.dev | pending delete | 2025 | 2 | 14 | — | — | 7 | |||
| proqura.dev | pending delete | 2025 | — | 0 | 0.13 | 1 | 8 | |||
| rslcode.dev | pending delete | 2025 | — | 0 | — | — | 9 | |||
| sterhak.dev | pending delete | 2025 | — | 0 | — | — | 10 | |||
| testbay.dev | pending delete | 2025 | — | 0 | — | — | 11 | |||
| thizara.dev | pending delete | 2025 | 1 | 2 | — | — | 12 | |||
| jewoolee.dev | pending delete | 2025 | — | 0 | — | — | 13 | |||
| runonaws.dev | pending delete | 2025 | — | 0 | — | — | 14 | |||
| chiapetta.dev | pending delete | 2025 | 0 | 4 | — | — | 15 | |||
| healthweb.dev | pending delete | 2025 | — | 0 | — | — | 16 | |||
| dataharbor.dev | pending delete | 2022 | 1 | 2 | — | — | 17 | |||
| elnino0916.dev | pending delete | 2025 | — | 0 | — | — | 18 | |||
| val-fatale.dev | pending delete | 2025 | — | 0 | — | — | 19 | |||
| dataharbour.dev | pending delete | 2022 | 1 | 2 | — | — | 20 | |||
| groundbreak.dev | pending delete | 2024 | 4 | 10 | — | — | 21 |
Take this list with you: this day as a CSV file · RSS feed · free datasets
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.