Skip to the page

Issue 2026-09-21The machinery behind this issue

Methods · 2026-09-21

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-09-21
arrived
246,713
resolved DNS
204,888
answered
141,630
looked custom
68,034
extracted
86,765
judged
999
catalogued
993

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
Civic & Public Life706982.31
Personal Pages222282.27
Weird Finds636382.24
Human Services151582.2
Developer Corner13413481.84
Content & Blogs777781.71
Oddly Specific323281.47
Learning & Exams555481.18
Food, Events & Hospitality111181.09
Useful Tools41441280.81
Commerce Shelf282880.68
AI Table353580.43
Suspicious Gentlemen222278.09
Local Businesses7777.71
Global Trade Desk121276.33
Template Sludge1043.0
Skip1020.0

05 · Before judging

Probe and landing classifications

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

Probe classifications
ClassificationDomains
custom_content_candidate58,751
no_dns41,825
client_error38,262
blank_or_tiny_page31,904
dns_only20,197
unknown_live19,293
parked_or_placeholder15,929
commercial_redirect8,602
server_error4,449
casino_or_betting3,345
login_or_admin_page1,997
under_construction1,097
app_or_tool_candidate549
domain_for_sale380
ai_or_tech_candidate132
unknown1
Landing categories
CategoryDomainsAvg score
thin_or_blank46,5010.74
business_or_project11,36677.78
summarizable_site5,98781.17
unknown_landing5,57045.75
developer_or_docs5,19283.14
product_or_saas3,47488.37
content_or_blog2,96373.29
sludge_or_spam2,31053.02
login_or_admin1,67120.18
extract_failed1,6080.0
non_html_asset1230.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.