The term "dotless domain" usually refers to top-level domains (TLDs) – think com, gov, etc – that are reachable themselves using a web browser or email server.
That is, they are working domains that consist of a single label: http://com/, as opposed to http://example.com/; or contact@gov, as opposed to [email protected]. This can happen if the domain's DNS zone contains A/AAAA or MX records in its apex.[1]
Both the ICANN and the IAB are notoriously against the practice,[1][2] so ICANN prohibits it where it can – namely, on gTLDs.[3] However, ccTLDs (country code TLDs) fall largely under their own country's jurisdiction! As such, there currently are and historically have been examples of active dotless ccTLDs.
For email, the protocol itself would need to allow a dotless domain as a destination address. According to ICANN's SSAC,[1] SMTP requires at least two labels (i.e. domain.tld) to deliver an email, so it is unlikely Mauritania would receive an email sent to contact@mr, for example. For completeness' sake, however, apex MX servers are listed below as well.
Table of Contents:
# A or AAAA
# Current
These are TLDs that, as of the last check, contain apex A or AAAA records. Many have had those records since the IETF compiled a list in 2013;[5] other dates indicate an observation by me, directly.
Territory | ccTLD | URL | IP (A/AAAA) |
Email server (MX) |
Status | First seen on |
---|---|---|---|---|---|---|
Bangladesh | .bd | http://bd/ | 203.112.194.232 | No |
|
Mar. 2025 |
Cameroon | .cm | http://cm/ | 195.24.205.60 | No |
|
2013 |
Tokelau (NZ) | .tk | http://tk/ | 217.119.57.22 | No |
|
2013 |
Uzbekistan | .uz | https://uz/ | 91.212.89.8 | No |
|
2013 |
Samoa | .ws | http://ws/ | 64.70.19.33 | mail.worldsite.ws |
|
2013 |
# Screenshots



(mirror of cctld.uz)
# New TLDs
In order to prevent local aliases from colliding with newly registered TLDs (think programmers using foo.bar as a test domain before the creation of the gTLD .bar), ICANN published a resolution in 2014 requiring new TLDs to include a few apex DNS records on their TLDs for at least 90 days.[4]
As of the last check, no TLDs had informational apex records. This is what they usually look like:
TLD | IP (A/AAAA) |
Email server (MX) |
Text record (TXT) |
---|---|---|---|
.example | 127.0.53.53 | your-dns-needs-immediate-attention.example | "Your DNS configuration needs immediate attention see https://icann.org/namecollision" |
# Historical
These are TLDs that previously had apex records, but no longer do so. Much of it comes from a list compiled by the IETF in 2013;[5] other dates indicate an observation by me, directly.
Territory | ccTLD | URL | IP (A/AAAA) |
Email server (MX) |
Known working date |
---|---|---|---|---|---|
Ascension (UK) | .ac | http://ac/ | 193.223.78.210 | No | 2013 |
Anguilla (UK) | .ai | http://ai/ | 209.59.119.34 | mail.offshore.ai | 2013— Jan. 2024 |
Bahrain | .bh | http://bh/ | 88.201.27.211 10.10.10.10 |
No | Aug. 2021— Jan. 2022 |
Denmark | .dk | http://dk/ | 193.163.102.24 [2a01:630:0:40:b1a:b1a:2011:1] |
No | 2013 |
Guernsey (UK) | .gg | http://gg/ | 87.117.196.80 | No | 2013 |
British Indian Ocean Territory (UK) |
.io | http://io/ | 193.223.78.212 | mailer2.io | 2013 |
Jersey (UK) | .je | http://je/ | 87.117.196.80 | No | 2013 |
Cambodia | .kh | http://kh/ | 203.223.32.21 | ns1.dns.net.kh | 2013 |
Pitcairn Islands (UK) | .pn | http://pn/ | 139.162.17.173 | No | Aug. 2021— Aug. 2023 |
Saint Helena (UK) | .sh | http://sh/ | 193.223.78.211 | No | 2013 |
Turkmenistan | .tm | http://tm/ | 193.223.78.213 | No | 2013 |
Tonga | .to | http://to/ | 216.74.32.107 | No | 2013 |
Vatican | .va | http://va/ | [2a01:b8:0:1:212:77:0:2] [2a01:b8:0:1:212:77:0:110] |
No | Aug. 2021— Jan. 2024 |
Virgin Islands (US) | .vi | http://vi/ | 193.0.0.198 | No | 2013 |
# Screenshots


(mirror of offshore.ai)


# MX only
# Current
These are TLDs that, as of the last check, contain only MX apex records; that is, they could, in theory, send and receive email, but have no reachable website. Many have had those records since the IETF compiled a list in 2013;[5] other dates indicate an observation by me, directly.
Territory | ccTLD | Email server (MX) |
First seen on |
---|---|---|---|
Central African Republic | .cf | mail.intnet.cf | 2013 |
Guadeloupe (FR) | .gp | ns1.nic.gp | 2013 |
Guatemala | .gt | aspmx2.googlemail.com aspmx4.googlemail.com aspmx5.googlemail.com aspmx.l.google.com alt1.aspmx.l.google.com alt2.aspmx.l.google.com |
2013 |
Croatia | .hr | alpha.carnet.hr | 2013 |
Comoros | .km | mail1.comorestelecom.km | 2013 |
Martinique (FR) | .mq | mx1-mq.mediaserv.net | 2013 |
Mauritania | .mr | mail.nic.mr | Aug. 2021 |
Trinidad and Tobago | .tt | aspmx.l.google.com alt1.aspmx.l.google.com |
2013 |
Ukraine | .ua | mr.kolo.net | 2013 |
# Historical
Similarly to the historical A/AAAA records, these are TLDs that previously (only) had apex MX records, but no longer do so. Many come from a list compiled by the IETF in 2013;[5] other dates indicate an observation by me, directly.
Territory | ccTLD | Email server (MX) |
Known working date |
---|---|---|---|
Åland Islands (FI) | .ax | mail.aland.net | 2013 |
Dominica | .dm | mail.nic.dm | 2013 |
Cambodia | .kh | ns1.dns.net.kh | Jan. 2022— Oct. 2022 |
Sri Lanka | .lk | malithi-slt.nic.lk malithi-lc.nic.lk |
2013— Jan. 2024 |
Panama | .pa | ns.pa | 2013— Jan. 2024 |
Philippines | .ph | mx1.sendnow.ph mx2.sendnow.ph mx3.sendnow.ph mx4.sendnow.ph mx5.sendnow.ph |
Aug. 2021— Oct. 2022 |
Suriname | .sr | spsbbank.sr | Aug. 2021— Jan. 2024 |
Vatican | .va | raphaelmx1.posta.va raphaelmx2.posta.va raphaelmx3.posta.va |
2013 |
Yemen | .ye | mail.yemen.net.ye | 2013 |
# Bonus: Dotless Dot?
Dotless domains work because top-level domains (TLDs) are just as much nodes in the DNS tree as second-level domains (SLDs), or any other level beneath them. That means there is no technicaly limitation to their DNS records, and they may contain A, AAAA and MX records.
Another, often forgotten node in the DNS tree is the root, represented by a single dot, .. It's the parent of all TLDs! Though it's usually omitted, every domain terminates with a dot: example.com is, in fact, example.com.; example is a child of com which, in turn, is a child of ..
Followed to its logical conclusion, this means the root domain could also contain A, AAAA and MX records! That is, accessing http://./ or emailing example@. is, at least in theory, possible.
Sadly, the odds of that ever happening are very nearly zero. The root doesn't have A, AAAA or MX records and likely won't, ever.
