# Automatic link creation for non-tld

**URL:** <https://meta.discourse.org/t/automatic-link-creation-for-non-tld/74387>\
**Category:** Support\
**Created:** [November 20, 2017, 1:38am UTC](https://meta.discourse.org/t/automatic-link-creation-for-non-tld/74387 "2017-11-20T01:38:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [November 20, 2017, 1:47am UTC](https://meta.discourse.org/t/automatic-link-creation-for-non-tld/74387/2 "2017-11-20T01:47:29Z")

</div>

Given ICANN’s predilection for stuffing the entire dictionary into the TLD space, it’s probably a losing proposition to try and whitelist _actual_ TLDs (as an amusing note, `.md` is a valid ccTLD, for Moldova, so even if we did have a list of “valid” TLDs, README.md is a perfectly valid domain name, and does, in fact, exist – and resolve).

For filenames, specifically, I suggest wrapping them in backticks, which maintains the long-standing convention of monospace fonts for that sort of thing, and which prevents auto-linkification, a la `README.md`. Trying to educate people to mark up their links in some specific way, such as wrapping them in angle brackets, or having to include the scheme, or including a forward slash, I think are all doomed to sadness.

---

_[View the full topic](https://meta.discourse.org/t/automatic-link-creation-for-non-tld/74387)._