📋 Ctrl+C, 🔐 Cryptographic 🌟 Easter 🥚 SEO 💥 Formatting 🔍 Admin 🌐 DNS 🌀 Pure 🔤 One 🤖 The 🏺 Ancient
📝 low bosp.co.uk

1. Entire XML sitemap pasted into DNS TXT record

The admin pasted their entire XML sitemap into a DNS TXT record. Search engine crawlers look for `sitemap.xml` at the web root — not inside a DNS text record. The `<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"...` tag sitting in global DNS will do absolutely nothing for their SEO.

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><url><loc>https://bosp.co.uk/</loc><lastmod>2024-01-15</lastmod><priority>1.00</priority></url><url><loc>https://bosp.co.uk/about</loc>...</url></urlset>

2. Facebook Meta Pixel JavaScript pasted into DNS

The admin pasted the full Facebook Meta Pixel JavaScript snippet — complete with the `!function(f,b,e,v,n,t,s)` obfuscated IIFE — into their DNS TXT record. JavaScript will never execute inside a DNS response. The Pixel has been tracking no one from inside that TXT record since the day it was added.

<script> !function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod?n.callMethod.apply(n,arguments):n.queue.push(arguments)};if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0';</script>

3. Raw HTML meta tag for Facebook verification in DNS

Facebook's domain verification instructions say "add this meta tag to your site's <head>". The admin instead pasted the raw `<meta name="facebook-domain-verification" content="..." />` HTML tag directly into their DNS TXT field. The DNS resolver dutifully returned the HTML tag to anyone who queried it — Facebook's crawler, however, never saw it.

<meta name="facebook-domain-verification" content="abc123xyz789def456" />

4. robots.txt configuration pasted into DNS

The admin pasted their entire robots.txt configuration directly into the DNS TXT record. "Sitemap: https://www.bramdeansleepers.co.uk/sitemap.xml | User-agent: * | Disallow: | Crawl-Delay: 30". Search engine crawlers look for robots.txt at the web root (yourdomain.com/robots.txt), not in a DNS text record. Googlebot will never see this.

Sitemap: https://www.bramdeansleepers.co.uk/sitemap.xml Sitemap: https://www.bramdeansleepers.co.uk/sitemap_pages.xml User-agent: * Disallow: Crawl-Delay: 30
📝 low celtest.co.uk

5. Using DNS as a corporate legal footer and trademark registry

Celtest Company Limited decided to use their global DNS zone as a permanent corporate legal notice board. The TXT record contains their company registration number, registered country, and trademark registration. No legal body will look for trademark registrations in DNS. But it is, in fairness, permanent and tamper-evident.

Celtest Company Limited is registered as a company in Wales. Company No. 1533370. celtest is a registered trademark within the UK of Celtest Company Limited IPO Reg. No. UK00003354743

6. Massive XML sitemap crammed into a TXT record

Another XML sitemap — a perfectly formatted one — pasted verbatim into a DNS TXT record. The `<urlset xmlns=...` declaration, the `<url>` elements, the `<loc>` tags, all of it. DNS TXT records are text. Googlebot looks for sitemaps on web servers. These two facts appear to have been unknown to this admin.

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <url><loc>https://conwydrainagesolutionsltd.co.uk/</loc><lastmod>2024-03-01</lastmod></url> ... </urlset>
📝 low cheaper99.co.uk

7. Sent a takedown request to the Wayback Machine via DNS

This admin attempted to send a formal exclusion request to the Internet Archive's Wayback Machine using a DNS TXT record. "URL/URL path to exclude: cheaper99.co.uk (and all subdomains) time period of domain ownership: 2022-03-21 to present." The Wayback Machine does not check DNS for takedown requests. This has never worked. It will never work.

URL/URL path to exclude: cheaper99.co.uk (and all subdomains) time period of domain ownership: 2022-03-21 to present time period to exclude: 2022-04-01 to future

Explore Other Categories