7 names match
| Domain Name | Status | Delete | Reg. | Age | History | Captures | Rank | RD | Actions | # |
|---|---|---|---|---|---|---|---|---|---|---|
| fimples.run | pending delete | 2025 | — | 0 | — | — | 1 | |||
| maxwell.run | pending delete | 2025 | — | 0 | — | — | 2 | |||
| rawagic.run | pending delete | 2025 | — | 0 | 0.26 | 1 | 3 | |||
| zhaopin.run | pending delete | 2025 | 8 | 1 | — | — | 4 | |||
| slotwins.run | pending delete | 2025 | — | 0 | 0.10 | 1 | 5 | |||
| officepaper.run | pending delete | 2025 | — | 0 | — | — | 6 | |||
| dottedtingly.run | pending delete | 2025 | — | 0 | — | — | 7 |
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.