| Domain Name | Status | Delete | Reg. | Age | History | Captures | Rank | RD | D | TLD | Actions | # |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bell.energy | pending delete | 2025 | 8 | 12 | — | — | — | — | 1 | |||
| solarbangladesh.energy | pending delete | 2023 | 1 | 2 | — | — | — | — | 2 | |||
| aifusion.energy | pending delete | 2025 | — | 0 | — | — | — | — | 3 | |||
| futurefusion.energy | pending delete | 2025 | — | 0 | — | — | — | — | 4 | |||
| astromining.energy | pending delete | 2025 | — | 0 | — | — | — | — | 5 | |||
| batterysalt.energy | pending delete | 2025 | — | 0 | — | — | — | — | 6 | |||
| crafty.energy | pending delete | 2025 | — | 0 | — | — | — | — | 7 | |||
| encase.energy | pending delete | 2025 | — | 0 | — | — | — | — | 8 | |||
| entity.energy | pending delete | 2025 | — | 0 | — | — | — | — | 9 | |||
| earning.energy | pending delete | 2025 | — | 0 | — | — | — | — | 10 | |||
| earthly.energy | pending delete | 2025 | 4 | 2 | — | — | — | — | 11 | |||
| helpful.energy | pending delete | 2025 | 3 | 2 | — | — | — | — | 12 | |||
| livable.energy | pending delete | 2025 | 8 | 6 | — | — | — | — | 13 | |||
| serving.energy | pending delete | 2025 | — | 0 | — | — | — | — | 14 | |||
| cleverly.energy | pending delete | 2025 | — | 0 | — | — | — | — | 15 | |||
| engaging.energy | pending delete | 2025 | — | 0 | — | — | — | — | 16 | |||
| enriching.energy | pending delete | 2025 | — | 0 | — | — | — | — | 17 | |||
| environment.energy | pending delete | 2025 | 8 | 4 | — | — | — | — | 18 | |||
| smartly.energy | pending delete | 2025 | 2 | 2 | 0.10 | 1 | — | — | 19 | |||
| infit.energy | pending delete | 2025 | 8 | 26 | — | — | — | — | 20 | |||
| edi.energy | pending delete | 2022 | — | 0 | — | — | — | — | 21 | |||
| peaknode.energy | pending delete | 2025 | — | 0 | — | — | — | — | 22 | |||
| 888.energy | pending delete | 2025 | 8 | 11 | 0.96 | 1 | — | — | 23 | |||
| auction.energy | pending delete | 2024 | 7 | 30 | 0.21 | 1 | — | — | 24 | |||
| mb66.energy | pending delete | 2025 | — | 0 | — | — | — | — | 25 | |||
| xcel.energy | pending delete | 2025 | 11 | 44 | 0.49 | 4 | — | — | 26 | |||
| summer.energy | pending delete | 2025 | 5 | 6 | — | — | — | — | 27 | |||
| human-ai.energy | available | 2025 | 1 | 1 | — | — | — | — | 28 | |||
| nationwidesolar.energy | available | 2022 | 3 | 22 | — | — | — | — | 29 | |||
| tez.energy | available | 2023 | 2 | 2 | — | — | — | — | 30 | |||
| cot.energy | available | 2025 | 2 | 6 | — | — | — | — | 31 | |||
| ruby.energy | available | 2023 | 2 | 17 | — | — | — | — | 32 | |||
| lura.energy | available | 2024 | 2 | 5 | — | — | — | — | 33 |
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.