# Capitalizing email domains and web addresses in correspondence

**URL:** <https://boards.straightdope.com/t/capitalizing-email-domains-and-web-addresses-in-correspondence/711896>\
**Category:** In My Humble Opinion\
**Created:** [February 5, 2015, 3:56pm UTC](https://boards.straightdope.com/t/capitalizing-email-domains-and-web-addresses-in-correspondence/711896 "2015-02-05T15:56:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/johnt/32/15048_2.png) [@JohnT](https://boards.straightdope.com/u/JohnT)\
**Post date:** [February 5, 2015, 3:56pm UTC](https://boards.straightdope.com/t/capitalizing-email-domains-and-web-addresses-in-correspondence/711896/1 "2015-02-05T15:56:11Z")

</div>

Simple question: If you have a company, say Johns Tech Company, and you have the domain [johnstechcompany.com](http://johnstechcompany.com), is it preferable on your correspondence\* to capitalize the words that comprise the domain?

Samples:

[Info@johnstechcompany.com](mailto:Info@johnstechcompany.com)  
…or…  
[Info@JohnsTechCompany.com](mailto:Info@JohnsTechCompany.com)

[www.johnstechcompany.com](http://www.johnstechcompany.com)  
…or…  
[www.JohnsTechCompany.com](http://www.JohnsTechCompany.com)

Public poll to follow…

\*Both print and electronic, though the issue that brought this question to mind was print (business cards)

---

<div class="post-metadata">

**Author:** ![control-z](https://avatars.discourse-cdn.com/v4/letter/c/eada6e/32.png) [@control-z](https://boards.straightdope.com/u/control-z)\
**Post date:** [February 5, 2015, 4:04pm UTC](https://boards.straightdope.com/t/capitalizing-email-domains-and-web-addresses-in-correspondence/711896/2 "2015-02-05T16:04:14Z")

</div>

I think there are good readability reasons to capitalize.

And no technical reasons not to capitalize that I know of, I know there are maybe a few old email systems that are case-sensitive, but it’s exceedingly rare.

---

<div class="post-metadata">

**Author:** ![Caldazar](https://avatars.discourse-cdn.com/v4/letter/c/8e8cbc/32.png) [@Caldazar](https://boards.straightdope.com/u/Caldazar)\
**Post date:** [February 5, 2015, 4:19pm UTC](https://boards.straightdope.com/t/capitalizing-email-domains-and-web-addresses-in-correspondence/711896/3 "2015-02-05T16:19:32Z")

</div>

In email addresses, the individual mail servers decide whether to treat the local-part of the address as case-sensitive or not (the part before the ‘@’). As **control-z** mentioned, email servers that treat addresses as case-sensitive are very rare. But you should still use all lowercase for the local-part just to avoid any potential issues with some goofy server out there treating ‘info@’ and ‘Info@’ differently.

Domain and hostnames are case-insensitive (the part after the ‘@’). Choose whichever you prefer; I personally prefer all lowercase for consistency with the local-part and so I don’t have to hit the shift key. I’m lazy like that.

I prefer the web address to be lowercase to align with the email addresses. Again, for consistency reasons.

---

<div class="post-metadata">

**Author:** ![filmore](https://avatars.discourse-cdn.com/v4/letter/f/7993a0/32.png) [@filmore](https://boards.straightdope.com/u/filmore)\
**Post date:** [February 5, 2015, 4:53pm UTC](https://boards.straightdope.com/t/capitalizing-email-domains-and-web-addresses-in-correspondence/711896/4 "2015-02-05T16:53:42Z")

</div>

You should never arbitrarily capitalize an email address since it’s up to the convention of the mail server whether it will consider all versions of the address to be the same. It may or may not consider info and INFO the same or different. It’s totally up to their own implementation.

Domain names, on the other hand, don’t care about case. The processing of them must be case insensitive. It’s part of the [RFC 1035](https://tools.ietf.org/html/rfc1035) standard:

> [@](#):
>
> 2.3.3. Character Case  
> For all parts of the DNS that are part of the official protocol, all  
> comparisons between character strings (e.g., labels, domain names, etc.)  
> are done in a case-insensitive manner.

Even though you can have capitals in the domain name, I would prefer not. First, it’s not commonly done so it looks odd. Second, it’s easier to type all the lower case than having the mixed case. Most people won’t know that they can type johnstechcompany or JohnsTechCompany, so they’ll type the mixed case.

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [February 6, 2015, 2:03am UTC](https://boards.straightdope.com/t/capitalizing-email-domains-and-web-addresses-in-correspondence/711896/5 "2015-02-06T02:03:18Z")

</div>

I’d say you should only possibly capitalize the domain if you have a CamelCase brand name, and your URL is also your brand name. For example, [GoDaddy.com](http://GoDaddy.com) makes sense. You could also capitalize if there would be confusion, like the classic [ExpertsExchange.com](http://ExpertsExchange.com).

For usernames, I would suggest using other separators besides capitals when making your names. Use [noparse]john.doe@johnstechcompany.com, not [JohnDoe@johnstechcompany.com](mailto:JohnDoe@johnstechcompany.com)[/noparse]. And never capitalize a single word like “info.”

Also, don’t use the “www” any more than you would include the “http://.” The only way it should be used is if it’s part of the brand. Any decent server will be configured to map [xxx.com](http://xxx.com) to [noparse][www.xxx.com](http://www.xxx.com)[/noparse].
