Skip to the page

Issue 2026-11-10The machinery behind this issue

Methods · 2026-11-10

How this issue was made

The machinery, filters, and editorial biases behind a daily field guide to newborn internet intentions.

01 · Process

From zone file to issue

The field narrows through network observation, extraction, scoring, model judgment, and publication gates.

  1. 01Arrivenew domains
  2. 02ProbeHTTP/HTTPS
  3. 03Classifylive or parked
  4. 04Extractlanding text
  5. 05Scorerules and signals
  6. 06Rankcandidate editor
  7. 07Judgepublication fit
  8. 08Publishissue and shelves

02 · Editorial position

Directional biases

The system is intentionally tuned toward things a curious reader might be glad to have seen.

Specificity over polish

Specific workflows, odd details, and concrete pages beat generic marketing language.

Operational detail over vibes

Receipts, mechanisms, forms, ledgers, APIs, rules, maps, and demos matter.

Human texture over templates

Local effort, personal attempts, care work, handmade pages, and strange missions receive a closer look.

Useful tools over generic SaaS

Narrow tools with a clear job usually beat broad productivity claims.

Oddness with evidence

Weird is good when the page has enough substance to understand what is happening.

Suspicion without promotion

Questionable pages may appear when they reveal a pattern, but they are framed critically.

Newly alive over merely registered

A name becomes interesting when it shows signs of public intent.

03 · Funnel

The narrowing

Counts are operational facts for this issue, not claims about the whole web.

batch date
2026-11-10
arrived
328,969
resolved DNS
269,699
answered
159,822
looked custom
92,728
extracted
116,266
judged
1,000
catalogued
984

04 · Public shelves

Editorial map

Judged counts cover the original candidates. Catalogued and shown counts reflect published cards after duplicate destinations are combined.

CategoryJudgedShownAverage interest
Human Services10981.6
Weird Finds848480.36
Civic & Public Life878479.61
Personal Pages171679.18
Content & Blogs707078.8
Developer Corner10710778.78
Learning & Exams494878.51
Oddly Specific413978.15
Local Businesses6678.0
Useful Tools46445977.84
AI Table9977.56
Commerce Shelf212176.95
Food, Events & Hospitality9876.56
Global Trade Desk3374.33
Suspicious Gentlemen212170.86
Skip2037.0

05 · Before judging

Probe and landing classifications

What the web probe saw and how extracted pages were grouped.

Probe classifications
ClassificationDomains
client_error86,208
custom_content_candidate79,254
no_dns59,270
unknown_live24,577
parked_or_placeholder24,536
dns_only18,104
commercial_redirect12,406
blank_or_tiny_page11,106
server_error4,999
casino_or_betting3,682
login_or_admin_page2,002
under_construction1,178
app_or_tool_candidate891
domain_for_sale578
ai_or_tech_candidate177
unknown1
Landing categories
CategoryDomainsAvg score
thin_or_blank51,7730.89
business_or_project11,92577.46
summarizable_site9,80083.87
product_or_saas8,71480.71
developer_or_docs7,87385.85
unknown_landing7,79345.2
login_or_admin6,5107.3
sludge_or_spam4,24651.4
content_or_blog4,18677.7
extract_failed3,3110.0
non_html_asset1350.0

06 · Limits

What this cannot tell us

Most domains are not meaningfully live on their birthday. Many do not answer at all; others resolve only to parking pages, placeholders, login screens, sales pages, or thin default templates. Domain Arrivals is a scan for the subset already visible enough to read, not a complete census.

The system can miss sites that block bots, load slowly, depend heavily on JavaScript, hide content behind forms, or say very little. It can over-reward pages that explain themselves clearly and under-reward quiet or primarily visual work.

Domain Arrivals is a field guide, not a certification system. A surfaced domain is not an endorsement.