Skip to the page

Issue 2026-09-16The machinery behind this issue

Methods · 2026-09-16

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-16
arrived
428,563
resolved DNS
349,164
answered
257,708
looked custom
135,325
extracted
166,615
judged
1,000
catalogued
1,000

04 · Public shelves

Editorial map

How judged candidates were distributed through the issue.

CategoryJudgedShownAverage interest
Weird Finds808083.44
Personal Pages181883.17
Learning & Exams353582.29
Content & Blogs828281.99
Oddly Specific303081.87
Civic & Public Life909081.66
Human Services151581.6
Developer Corner12412481.44
Useful Tools41641681.19
Commerce Shelf252580.76
Food, Events & Hospitality161680.44
Global Trade Desk131380.38
AI Table343480.35
Local Businesses6680.33
Suspicious Gentlemen161680.25

05 · Before judging

Probe and landing classifications

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

Probe classifications
ClassificationDomains
custom_content_candidate116,167
no_dns79,399
client_error60,347
blank_or_tiny_page59,779
unknown_live32,764
dns_only22,340
parked_or_placeholder18,459
commercial_redirect18,159
server_error8,131
casino_or_betting6,298
login_or_admin_page3,075
under_construction1,996
app_or_tool_candidate779
domain_for_sale649
ai_or_tech_candidate220
unknown1
Landing categories
CategoryDomainsAvg score
thin_or_blank94,9640.57
business_or_project23,80175.26
summarizable_site9,49681.96
developer_or_docs9,08282.55
unknown_landing7,77646.28
product_or_saas5,80288.18
content_or_blog5,03374.71
sludge_or_spam4,26449.68
login_or_admin3,30125.33
extract_failed2,9840.0
non_html_asset1120.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.