| Domain Name | Status | Delete | Reg. | Age | History | Captures | Rank | RD | D | TLD | Actions | # |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| youtiao.team | pending delete | 2022 | 3 | 9 | — | — | — | — | 1 | |||
| fairsrteam20251964.team | pending delete | 2025 | 1 | 2 | — | — | — | — | 2 | |||
| niwo.team | pending delete | 2024 | 2 | 15 | — | — | — | — | 3 | |||
| ruiliantouzi.team | pending delete | 2025 | — | 0 | — | — | — | — | 4 | |||
| aid-whtsapp.team | pending delete | 2025 | — | 0 | — | — | — | — | 5 | |||
| fairy.team | pending delete | 2025 | 8 | 5 | — | — | — | — | 6 | |||
| qz8848.team | pending delete | 2025 | — | 0 | — | — | — | — | 7 | |||
| consensus.team | pending delete | 2025 | 8 | 5 | — | — | — | — | 8 | |||
| lavrikov.team | pending delete | 2023 | — | 0 | — | — | — | — | 9 | |||
| borealtradex.team | pending delete | 2025 | — | 0 | — | — | — | — | 10 | |||
| gurman.team | pending delete | 2023 | — | 0 | — | — | — | — | 11 | |||
| ingosstrah.team | pending delete | 2024 | 2 | 18 | — | — | — | — | 12 | |||
| placeme.team | pending delete | 2019 | 5 | 26 | 1.32 | 1 | — | — | 13 | |||
| thelaunchers.team | pending delete | 2025 | — | 0 | — | — | — | — | 14 | |||
| thanks.team | pending delete | 2025 | 8 | 24 | — | — | — | — | 15 | |||
| into.team | pending delete | 2025 | 5 | 5 | — | — | — | — | 16 | |||
| immersive.team | pending delete | 2025 | 4 | 8 | — | — | — | — | 17 | |||
| leadingedge.team | pending delete | 2025 | — | 0 | — | — | — | — | 18 | |||
| brookhollow.team | pending delete | 2025 | — | 0 | — | — | — | — | 19 | |||
| pssi.team | available | 2024 | 2 | 5 | — | — | — | — | 20 | |||
| pixellab.team | available | 2023 | 2 | 23 | — | — | — | — | 21 | |||
| gangbang.team | available | 2025 | 8 | 2 | — | — | — | — | 22 | |||
| assfuck.team | available | 2025 | — | 0 | — | — | — | — | 23 | |||
| foxleads-proxy.team | available | 2023 | 2 | 15 | — | — | — | — | 24 | |||
| foxleads-crm.team | available | 2023 | 2 | 21 | — | — | — | — | 25 | |||
| tanja-mayerhofer.team | available | 2025 | — | 0 | — | — | — | — | 26 | |||
| streamer.team | available | 2025 | 4 | 5 | — | — | — | — | 27 | |||
| comeback.team | available | 2025 | 5 | 18 | 0.37 | 1 | — | — | 28 | |||
| wmg.team | available | 2025 | — | 0 | — | — | — | — | 29 | |||
| widdershins.team | available | 2025 | 0 | 5 | — | 0 | — | — | 30 | |||
| pleasedoit.team | available | 2019 | 4 | 1 | — | — | — | — | 31 | |||
| alo789.team | available | 2023 | 2 | 15 | — | — | — | — | 32 | |||
| loud.team | available | 2025 | 4 | 7 | — | — | — | — | 33 | |||
| helo.team | available | 2022 | 2 | 5 | — | — | — | — | 34 |
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.