<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: domains</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/domains.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2026-02-15T17:23:28+00:00</updated><author><name>Simon Willison</name></author><entry><title>Three months of OpenClaw</title><link href="https://simonwillison.net/2026/Feb/15/openclaw/#atom-tag" rel="alternate"/><published>2026-02-15T17:23:28+00:00</published><updated>2026-02-15T17:23:28+00:00</updated><id>https://simonwillison.net/2026/Feb/15/openclaw/#atom-tag</id><summary type="html">
    &lt;p&gt;It's wild that the first commit to OpenClaw was &lt;a href="https://github.com/openclaw/openclaw/commit/f6dd362d39b8e30bd79ef7560aab9575712ccc11"&gt;on November 25th 2025&lt;/a&gt;, and less than three months later it's hit 10,000 commits from 600 contributors, attracted 196,000 GitHub stars and sort-of been featured in an extremely vague &lt;a href="https://www.youtube.com/watch?v=n7I-D4YXbzg"&gt;Super Bowl commercial for AI.com&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Quoting AI.com founder &lt;a href="https://twitter.com/kris/status/2020663711015514399"&gt;Kris Marszalek&lt;/a&gt;, purchaser of the &lt;a href="https://www.theregister.com/2026/02/09/70m_aicom_domain_sale/"&gt;most expensive domain in history&lt;/a&gt; for $70m:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;ai.com is the world’s first easy-to-use and secure implementation of OpenClaw, the open source agent framework that went viral two weeks ago; we made it easy to use without any technical skills, while hardening security to keep your data safe.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Looks like vaporware to me - all you can do right now is reserve a handle - but it's still remarkable to see an open source project get to &lt;em&gt;that&lt;/em&gt; level of hype in such a short space of time.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt;: OpenClaw creator Peter Steinberger &lt;a href="https://steipete.me/posts/2026/openclaw"&gt;just announced&lt;/a&gt; that he's joining OpenAI and plans to transfer ownership of OpenClaw to a new independent foundation.&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/ai-agents"&gt;ai-agents&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openclaw"&gt;openclaw&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/open-source"&gt;open-source&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openai"&gt;openai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/peter-steinberger"&gt;peter-steinberger&lt;/a&gt;&lt;/p&gt;



</summary><category term="ai-agents"/><category term="openclaw"/><category term="ai"/><category term="open-source"/><category term="domains"/><category term="openai"/><category term="peter-steinberger"/></entry><entry><title>PyPI: Preventing Domain Resurrection Attacks</title><link href="https://simonwillison.net/2025/Aug/19/pypi-preventing-domain-resurrection-attacks/#atom-tag" rel="alternate"/><published>2025-08-19T15:36:44+00:00</published><updated>2025-08-19T15:36:44+00:00</updated><id>https://simonwillison.net/2025/Aug/19/pypi-preventing-domain-resurrection-attacks/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://blog.pypi.org/posts/2025-08-18-preventing-domain-resurrections/"&gt;PyPI: Preventing Domain Resurrection Attacks&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Domain resurrection attacks are a nasty vulnerability in systems that use email verification to allow people to recover their accounts. If somebody lets their domain name expire an attacker might snap it up and use it to gain access to their accounts - which can turn into a package supply chain attack if they had an account on something like the Python Package Index.&lt;/p&gt;
&lt;p&gt;PyPI now protects against these by treating an email address as not-validated if the associated domain expires.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Since early June 2025, PyPI has unverified over 1,800 email addresses when their associated domains entered expiration phases. This isn't a perfect solution, but it closes off a significant attack vector where the majority of interactions would appear completely legitimate.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This attack is not theoretical: it happened to the &lt;code&gt;ctx&lt;/code&gt; package on PyPI &lt;a href="https://python-security.readthedocs.io/pypi-vuln/index-2022-05-24-ctx-domain-takeover.html"&gt;back in May 2022&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Here's the &lt;a href="https://github.com/pypi/warehouse/pull/17832"&gt;pull request&lt;/a&gt; from April in which Mike Fiedler landed an integration which hits an API provided by Fastly's &lt;a href="https://domainr.com/"&gt;Domainr&lt;/a&gt;, followed by &lt;a href="https://github.com/pypi/warehouse/pull/18014"&gt;this PR&lt;/a&gt; which &lt;a href="https://github.com/miketheman/warehouse/blob/48f082b4fb085a25dabdb87c2e158af04b1ba5e8/warehouse/accounts/tasks.py#L141-L164"&gt;polls for domain status&lt;/a&gt; on any email domain that hasn't been checked in the past 30 days.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="https://news.ycombinator.com/item?id=44950091"&gt;Hacker News&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/pypi"&gt;pypi&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/supply-chain"&gt;supply-chain&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="pypi"/><category term="python"/><category term="security"/><category term="supply-chain"/></entry><entry><title>Ask HN: What happens to ".io" TLD after UK gives back the Chagos Islands?</title><link href="https://simonwillison.net/2024/Oct/3/what-happens-to-io-after-uk-gives-back-chagos/#atom-tag" rel="alternate"/><published>2024-10-03T17:25:21+00:00</published><updated>2024-10-03T17:25:21+00:00</updated><id>https://simonwillison.net/2024/Oct/3/what-happens-to-io-after-uk-gives-back-chagos/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://news.ycombinator.com/item?id=41729526"&gt;Ask HN: What happens to &amp;quot;.io&amp;quot; TLD after UK gives back the Chagos Islands?&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
This morning on the BBC: &lt;a href="https://www.bbc.com/news/articles/c98ynejg4l5o"&gt;UK will give sovereignty of Chagos Islands to Mauritius&lt;/a&gt;. The Chagos Islands include the area that the UK calls &lt;a href="https://en.wikipedia.org/wiki/British_Indian_Ocean_Territory"&gt;the British Indian Ocean Territory&lt;/a&gt;. The &lt;a href="https://en.wikipedia.org/wiki/.io"&gt;.io ccTLD&lt;/a&gt; uses the  ISO-3166 two-letter country code for that designation.&lt;/p&gt;
&lt;p&gt;As the owner of &lt;a href="https://datasette.io/"&gt;datasette.io&lt;/a&gt; the question of what happens to that ccTLD is suddenly very relevant to me.&lt;/p&gt;
&lt;p&gt;This Hacker News conversation has some useful information. It sounds like there's a very real possibility that &lt;code&gt;.io&lt;/code&gt; could be deleted after a few years notice - it's happened before, for ccTLDs such as &lt;code&gt;.zr&lt;/code&gt; for Zaire (which renamed to &lt;a href="https://en.wikipedia.org/wiki/Democratic_Republic_of_the_Congo"&gt;Democratic Republic of the Congo&lt;/a&gt; in 1997, with &lt;code&gt;.zr&lt;/code&gt; withdrawn in 2001) and &lt;a href="https://en.wikipedia.org/wiki/.cs"&gt;.cs&lt;/a&gt; for Czechoslovakia, withdrawn in 1995.&lt;/p&gt;
&lt;p&gt;Could &lt;code&gt;.io&lt;/code&gt; change status to the same kind of TLD as &lt;code&gt;.museum&lt;/code&gt;, unaffiliated with any particular geography? The convention is for two letter TLDs to exactly match ISO country codes, so that may not be an option.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/dns"&gt;dns&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/hacker-news"&gt;hacker-news&lt;/a&gt;&lt;/p&gt;



</summary><category term="dns"/><category term="domains"/><category term="hacker-news"/></entry><entry><title>Every remaining website using the .museum TLD</title><link href="https://simonwillison.net/2022/Nov/20/every-remaining-website-using-the-museum-tld/#atom-tag" rel="alternate"/><published>2022-11-20T00:53:44+00:00</published><updated>2022-11-20T00:53:44+00:00</updated><id>https://simonwillison.net/2022/Nov/20/every-remaining-website-using-the-museum-tld/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://gist.github.com/Jonty/c3c870245c859d1ffa85b85c45a654f5"&gt;Every remaining website using the .museum TLD&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Jonty did a survey of every one of the 1,134 domains using the .museum TLD, which dates back to 2001 and is managed by The Museum Domain Management Association.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="https://fedi.simonwillison.net/@jonty@chaos.social/109349106322530749"&gt;@jonty@chaos.social&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/museums"&gt;museums&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="museums"/></entry><entry><title>How CDNs Generate Certificates</title><link href="https://simonwillison.net/2020/Jun/26/how-cdns-generate-certificates/#atom-tag" rel="alternate"/><published>2020-06-26T00:03:45+00:00</published><updated>2020-06-26T00:03:45+00:00</updated><id>https://simonwillison.net/2020/Jun/26/how-cdns-generate-certificates/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://fly.io/blog/how-cdns-generate-certificates/"&gt;How CDNs Generate Certificates&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Thomas Ptacek (now at Fly) describes in intricate detail the challenges faced by large-scale hosting providers that want to securely issue LetsEncrypt certificates for customer domains. Lots of detail here on the different ACME challenges supported by LetsEncrypt and why the new tls-alpn-01 challenge is the right option for operating at scale.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/acme"&gt;acme&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/certificates"&gt;certificates&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/thomas-ptacek"&gt;thomas-ptacek&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tls"&gt;tls&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/fly"&gt;fly&lt;/a&gt;&lt;/p&gt;



</summary><category term="acme"/><category term="certificates"/><category term="domains"/><category term="thomas-ptacek"/><category term="tls"/><category term="fly"/></entry><entry><title>The death of a TLD</title><link href="https://simonwillison.net/2018/Jul/28/death-tld/#atom-tag" rel="alternate"/><published>2018-07-28T20:07:00+00:00</published><updated>2018-07-28T20:07:00+00:00</updated><id>https://simonwillison.net/2018/Jul/28/death-tld/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://blog.benjojo.co.uk/post/the-death-of-a-tld"&gt;The death of a TLD&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Sony have terminated their .xperia TLD. Ben Cox used Certificate Transparency logs to evaluate the 11 total TLDs that have been abandoned since the gTLD gold rush started—since HTTPS is becoming the default now these logs of issued certificates are a great indicator of which domains (or TLDs) are being actively used. The only deleted TLD with legitimate looking certificates (apparently for a  mail server) was .mcdonalds


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/certificates"&gt;certificates&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/dns"&gt;dns&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tls"&gt;tls&lt;/a&gt;&lt;/p&gt;



</summary><category term="certificates"/><category term="dns"/><category term="domains"/><category term="tls"/></entry><entry><title>Domains Search for Web: Instant, Serverless &amp; Global</title><link href="https://simonwillison.net/2018/Jan/26/domains-search/#atom-tag" rel="alternate"/><published>2018-01-26T01:14:52+00:00</published><updated>2018-01-26T01:14:52+00:00</updated><id>https://simonwillison.net/2018/Jan/26/domains-search/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://zeit.co/blog/domains-search-web"&gt;Domains Search for Web: Instant, Serverless &amp;amp; Global&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
The team at Zeit are pioneering a whole bunch of fascinating web engineering architectural patterns. Their new domain name autocomplete search uses Next.js and server-side rendering on first load, then switches to client-side rendering from then on. It can then load results asynchronously over a custom WebSocket protocol as the microservices on the backend finish resolving domain availability from the various different TLD providers.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="https://twitter.com/rauchg/status/956402473354366977"&gt;Guillermo Rauch‏&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/websockets"&gt;websockets&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/zeit-now"&gt;zeit-now&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/microservices"&gt;microservices&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="websockets"/><category term="zeit-now"/><category term="microservices"/></entry><entry><title>SSL Issuer Popularity</title><link href="https://simonwillison.net/2017/Nov/21/ssl-issuer-popularity/#atom-tag" rel="alternate"/><published>2017-11-21T14:44:56+00:00</published><updated>2017-11-21T14:44:56+00:00</updated><id>https://simonwillison.net/2017/Nov/21/ssl-issuer-popularity/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://nettrack.info/ssl_certificate_issuers.html"&gt;SSL Issuer Popularity&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
The impressive growth of Let’s Encrypt in one graph: from 4.87% of TLS-enabled domains in May 2016 to 36.68% in November 2017.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ssl"&gt;ssl&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="ssl"/></entry><entry><title>What is the best service for web hosting and buying a domain? Is it better to have both under one provider?</title><link href="https://simonwillison.net/2013/Sep/22/what-is-the-best/#atom-tag" rel="alternate"/><published>2013-09-22T15:12:00+00:00</published><updated>2013-09-22T15:12:00+00:00</updated><id>https://simonwillison.net/2013/Sep/22/what-is-the-best/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/What-is-the-best-service-for-web-hosting-and-buying-a-domain-Is-it-better-to-have-both-under-one-provider/answer/Simon-Willison"&gt;What is the best service for web hosting and buying a domain? Is it better to have both under one provider?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;No, it's not better to have both under the same provider. Good web hosts do not necessarily make good DNS hosts and vice versa.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/hosting"&gt;hosting&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/web-development"&gt;web-development&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="domains"/><category term="hosting"/><category term="web-development"/><category term="quora"/></entry><entry><title>How did art.sy get a ".sy" url?</title><link href="https://simonwillison.net/2012/May/31/how-did-artsy-get/#atom-tag" rel="alternate"/><published>2012-05-31T11:00:00+00:00</published><updated>2012-05-31T11:00:00+00:00</updated><id>https://simonwillison.net/2012/May/31/how-did-artsy-get/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/How-did-art-sy-get-a-sy-url/answer/Simon-Willison"&gt;How did art.sy get a &amp;quot;.sy&amp;quot; url?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Here's a generally useful tip: if you're interested in learning more about ANY top level domain, visit the Wikipedia page for it - which will be &lt;span&gt;&lt;a href="http://en.wikipedia.org/wiki/.sy"&gt;http://en.wikipedia.org/wiki/.sy&lt;/a&gt;&lt;/span&gt; in this case (just add the domain, complete with its dot prefix, directly after &lt;span&gt;&lt;a href="http://en.wikipedia.org/wiki/"&gt;en.wikipedia.org/wiki/&lt;/a&gt;&lt;/span&gt; ).&lt;/p&gt;

&lt;p&gt;The wikipedia page will tell you which country the domain refers to, who the registrar is, what restrictions there are on those domains and plenty more besides. In this case, .sy is Syria - not exactly the best country to be associating your brand with these days!&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/urls"&gt;urls&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/wikipedia"&gt;wikipedia&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="domains"/><category term="urls"/><category term="wikipedia"/><category term="quora"/></entry><entry><title>Are there any disadvantages to using domain hacks for your product website?</title><link href="https://simonwillison.net/2012/Jan/16/are-there-any-disadvantages/#atom-tag" rel="alternate"/><published>2012-01-16T16:29:00+00:00</published><updated>2012-01-16T16:29:00+00:00</updated><id>https://simonwillison.net/2012/Jan/16/are-there-any-disadvantages/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/Are-there-any-disadvantages-to-using-domain-hacks-for-your-product-website/answer/Simon-Willison"&gt;Are there any disadvantages to using domain hacks for your product website?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If you ever get written up&lt;br /&gt;In the mainstream press you can almost guarantee that they will screw up the URL they publish (by sticking a .com on the end or fixing a deliberate misspelling). Sadly this still seems to be the case after 20 years of the Web!&lt;/p&gt;

&lt;p&gt;Scary story about this here: &lt;span&gt;&lt;a href="http://www.skrenta.com/2007/03/kafkaesque.html"&gt;http://www.skrenta.com/2007/03/k...&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/web-development"&gt;web-development&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="domains"/><category term="web-development"/><category term="quora"/></entry><entry><title>Why is Google indexing &amp; displaying www1 versions of my site and how might I stop this?</title><link href="https://simonwillison.net/2012/Jan/9/why-is-google-indexing/#atom-tag" rel="alternate"/><published>2012-01-09T12:43:00+00:00</published><updated>2012-01-09T12:43:00+00:00</updated><id>https://simonwillison.net/2012/Jan/9/why-is-google-indexing/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/Why-is-Google-indexing-displaying-www1-versions-of-my-site-and-how-might-I-stop-this/answer/Simon-Willison"&gt;Why is Google indexing &amp;amp; displaying www1 versions of my site and how might I stop this?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You should stop serving your site to the public on multiple subdomains. Configure your site to serve a 301 permanent redirect from www1-www4 to the equivalent page on www - also, make sure that your site accessed without the www redirects to the right place as well.&lt;/p&gt;

&lt;p&gt;The use of 301s will avoid any SEO penalty.&lt;/p&gt;

&lt;p&gt;Why should you take this relatively extreme measure? Because serving on multiple subdomains hurts you in a bunch if ways:&lt;/p&gt;

&lt;p&gt;1) Your SEO is spread across multiple copies of the same page, hurting your page rank.&lt;/p&gt;

&lt;p&gt;2) Your cookies may end up spread across multiple domains, hurting your analytics and resulting in frustrated users who are signed in on only some of your subdomains&lt;/p&gt;

&lt;p&gt;3) You're damaging your scores on social media sharing sites. To use quite an old example, delicious used to use the number of bookmarks to a unique URL to decide what would appear on their "popular" page. Having multiple URLs for a piece of content split that score, making it much less likely you would appear there.&lt;/p&gt;

&lt;p&gt;4) You're making life harder for yourself should you need to switch to serving your entire site over SSL (which you may need to do to see Google search referral information as they move more of their search results pages to SSL)&lt;/p&gt;

&lt;p&gt;Using rel=canonical is a good short-term fix, but it's not too hate to implement the proper 301 fix and in my opinion it's well worth the effort.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/search-engines"&gt;search-engines&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/seo"&gt;seo&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="domains"/><category term="google"/><category term="search-engines"/><category term="seo"/><category term="quora"/></entry><entry><title>Why don't more websites use alternative domains?</title><link href="https://simonwillison.net/2010/Oct/13/why-dont-more-websites/#atom-tag" rel="alternate"/><published>2010-10-13T11:49:00+00:00</published><updated>2010-10-13T11:49:00+00:00</updated><id>https://simonwillison.net/2010/Oct/13/why-dont-more-websites/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/Why-dont-more-websites-use-alternative-domains/answer/Simon-Willison"&gt;Why don&amp;#39;t more websites use alternative domains?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Because regular human beings don't understand them, and expect everything to be a .com. Here's an interesting post from 2007 on why &lt;span&gt;&lt;a href="http://Topix.net"&gt;Topix.net&lt;/a&gt;&lt;/span&gt; spent $1,000,000 buying the .com domain: &lt;span&gt;&lt;a href="http://www.skrenta.com/2007/03/kafkaesque.html"&gt;http://www.skrenta.com/2007/03/k...&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/urls"&gt;urls&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="domains"/><category term="urls"/><category term="quora"/></entry><entry><title>Is the .ly domain unsafe? Why?</title><link href="https://simonwillison.net/2010/Oct/12/is-the-ly-domain/#atom-tag" rel="alternate"/><published>2010-10-12T15:27:00+00:00</published><updated>2010-10-12T15:27:00+00:00</updated><id>https://simonwillison.net/2010/Oct/12/is-the-ly-domain/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/Is-the-ly-domain-unsafe-Why/answer/Simon-Willison"&gt;Is the .ly domain unsafe? Why?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;It's always been unsafe in my opinion. Why build your company around a domain name that's controlled by the Libyan government?&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="domains"/><category term="quora"/></entry><entry><title>Why do so many Internet sites end with the letter 'r' (but not 'er')?  Think about Tumblr, Dopplr, Migratr.  What's behind this?</title><link href="https://simonwillison.net/2010/Sep/8/why-do-so-many/#atom-tag" rel="alternate"/><published>2010-09-08T13:52:00+00:00</published><updated>2010-09-08T13:52:00+00:00</updated><id>https://simonwillison.net/2010/Sep/8/why-do-so-many/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/Why-do-so-many-Internet-sites-end-with-the-letter-r-but-not-er-Think-about-Tumblr-Dopplr-Migratr-Whats-behind-this/answer/Simon-Willison"&gt;Why do so many Internet sites end with the letter &amp;#39;r&amp;#39; (but not &amp;#39;er&amp;#39;)?  Think about Tumblr, Dopplr, Migratr.  What&amp;#39;s behind this?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;We just launched a project called lanyrd, which is a play on lanyard. We partly picked the name because the domain was available, but there's actually a big advantage to using a made-up word: it's really easy to search for coverage and feedback on Twitter, Google Blogsearch and the like. The string "lanyrd" is almost exclusively used to discuss our project - had we used a dictionary word, tracking down feedback would have been a lot harder.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/internet"&gt;internet&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="domains"/><category term="internet"/><category term="quora"/></entry><entry><title>Some People Can't Read URLs</title><link href="https://simonwillison.net/2010/Mar/2/bewildering/#atom-tag" rel="alternate"/><published>2010-03-02T10:16:09+00:00</published><updated>2010-03-02T10:16:09+00:00</updated><id>https://simonwillison.net/2010/Mar/2/bewildering/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://jonoscript.wordpress.com/2010/02/18/some-people-cant-read-urls/"&gt;Some People Can&amp;#x27;t Read URLs&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Commentary on the recent “facebook login” incident from Jono at Mozilla Labs. I’d guess that most people can’t read URLs, and it worries me more than any other aspect of today’s web. If you want to stay safe from phishing and other forms of online fraud you need at least a basic understanding of a bewildering array of technologies—URLs, paths, domains, subdomains, ports, DNS, SSL as well as fundamental concepts like browsers, web sites and web servers. Misunderstand any of those concepts and you’ll be an easy target for even the most basic phishing attempts. It almost makes me uncomfortable encouraging regular people to use the web because I know they’ll be at massive risk to online fraud.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/facebook"&gt;facebook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/phishing"&gt;phishing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/urls"&gt;urls&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="facebook"/><category term="phishing"/><category term="security"/><category term="urls"/></entry><entry><title>Dangers of remote Javascript</title><link href="https://simonwillison.net/2008/Jan/20/dangers/#atom-tag" rel="alternate"/><published>2008-01-20T09:49:06+00:00</published><updated>2008-01-20T09:49:06+00:00</updated><id>https://simonwillison.net/2008/Jan/20/dangers/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://radar.oreilly.com/archives/2008/01/dangers_of_remo.html"&gt;Dangers of remote Javascript&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Perl.com got hit by a JavaScript porn redirect when the domain of one of their advertisers expired and was bought by a porn company. Nat Torkington suggests keeping track of the expiration dates on any third party domains that are serving JavaScript on your site.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/nat-torkington"&gt;nat-torkington&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oreilly"&gt;oreilly&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/perldotcom"&gt;perldotcom&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/xss"&gt;xss&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="javascript"/><category term="nat-torkington"/><category term="oreilly"/><category term="perldotcom"/><category term="security"/><category term="xss"/></entry><entry><title>UK domain registrar 123-Reg crashes and burns, taking its customers with it</title><link href="https://simonwillison.net/2007/Nov/18/uk/#atom-tag" rel="alternate"/><published>2007-11-18T11:24:07+00:00</published><updated>2007-11-18T11:24:07+00:00</updated><id>https://simonwillison.net/2007/Nov/18/uk/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blogs.cnet.com/8301-13505_1-9819551-16.html"&gt;UK domain registrar 123-Reg crashes and burns, taking its customers with it&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I was hit by this yesterday: can anyone recommend an alternative DNS host with a really easy to use interface (I’ve made mistakes modifying DNS in the past) and rock-solid reliability?


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/123reg"&gt;123reg&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/dns"&gt;dns&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;&lt;/p&gt;



</summary><category term="123reg"/><category term="dns"/><category term="domains"/></entry><entry><title>Bust A Name</title><link href="https://simonwillison.net/2007/Aug/20/bustaname/#atom-tag" rel="alternate"/><published>2007-08-20T15:40:01+00:00</published><updated>2007-08-20T15:40:01+00:00</updated><id>https://simonwillison.net/2007/Aug/20/bustaname/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.bustaname.com/"&gt;Bust A Name&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Smart Ajax powered domain search; you give it some words, it shows you available combinations. It’s still almost impossible to find something that doesn’t suck though.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/ajax"&gt;ajax&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/bustaname"&gt;bustaname&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rails"&gt;rails&lt;/a&gt;&lt;/p&gt;



</summary><category term="ajax"/><category term="bustaname"/><category term="domains"/><category term="rails"/></entry><entry><title>FreeYourID.com</title><link href="https://simonwillison.net/2007/Feb/13/free/#atom-tag" rel="alternate"/><published>2007-02-13T16:26:50+00:00</published><updated>2007-02-13T16:26:50+00:00</updated><id>https://simonwillison.net/2007/Feb/13/free/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.freeyourid.com/"&gt;FreeYourID.com&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
A free .name domain for 90 days, with built-in tools for managing e-mail forwarding and your OpenID. Could  do with some unobtrusive JavaScript, but they’re really fast at responding to suggestions.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/freeyourid"&gt;freeyourid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="freeyourid"/><category term="openid"/></entry><entry><title>Details of Google's Latest Security Hole</title><link href="https://simonwillison.net/2007/Jan/14/google/#atom-tag" rel="alternate"/><published>2007-01-14T13:36:59+00:00</published><updated>2007-01-14T13:36:59+00:00</updated><id>https://simonwillison.net/2007/Jan/14/google/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.outer-court.com/archive/2007-01-14-n21.html"&gt;Details of Google&amp;#x27;s Latest Security Hole&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
For a brief while you could use Blogger Custom Domains to point a Google subdomain at your own content, letting you hijack Google cookies and steal accounts for any Google services.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/domainsecurity"&gt;domainsecurity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/xss"&gt;xss&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="domainsecurity"/><category term="google"/><category term="security"/><category term="xss"/></entry><entry><title>TBL on TLDs</title><link href="https://simonwillison.net/2004/May/22/tbl/#atom-tag" rel="alternate"/><published>2004-05-22T06:23:35+00:00</published><updated>2004-05-22T06:23:35+00:00</updated><id>https://simonwillison.net/2004/May/22/tbl/#atom-tag</id><summary type="html">
    &lt;p&gt;Tim Berners Lee (how many &lt;acronym title="Three Letter Acronym"&gt;TLA&lt;/acronym&gt; celebrities is that now?): &lt;a href="http://www.w3.org/DesignIssues/TLD"&gt;New Top Level Domains Considered Harmful&lt;/a&gt;. Read the whole thing - Tim blows the .xxx and .mobi proposals out of the water and takes a neat swipe at for-profit registrars in the process. Reading this, the main thing that struck me is how incredibly forward thinking &lt;acronym title="Tim Berners Lee"&gt;TBL&lt;/acronym&gt; really is. People complain about the long duration of &lt;acronym title="World Wide Web Consortium"&gt;W3C&lt;/acronym&gt; processes and the futuristic nature of the semantic web but the &lt;acronym title="World Wide Web Consortium"&gt;W3C&lt;/acronym&gt; are trying to build technologies that will still be relevant ten or twenty years from now. When you consider the longevity of &lt;acronym title="Transfer Control Protocol / Internet Protocol"&gt;TCP/IP&lt;/acronym&gt;, this is a really smart strategy. It's a shame so many people involved with the web have trouble thinking past the next few months.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tim-berners-lee"&gt;tim-berners-lee&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/urls"&gt;urls&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/w3c"&gt;w3c&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="domains"/><category term="tim-berners-lee"/><category term="urls"/><category term="w3c"/></entry></feed>