Skip to the page

Issue 2026-11-16The machinery behind this issue

Methods · 2026-11-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-11-16
arrived
259,594
resolved DNS
208,997
answered
148,227
looked custom
92,114
extracted
117,400
judged
1,000
catalogued
971

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 Life908980.81
Personal Pages171680.06
Weird Finds736579.6
Learning & Exams585679.52
Developer Corner676678.84
Content & Blogs797778.71
Food, Events & Hospitality9878.22
Useful Tools48847977.95
Oddly Specific434377.81
Commerce Shelf161677.75
Local Businesses3377.67
Human Services141477.43
AI Table111177.18
Global Trade Desk5576.8
Suspicious Gentlemen232372.48
Still Interesting, But Barely1054.0
Skip3040.67

05 · Before judging

Probe and landing classifications

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

Probe classifications
ClassificationDomains
custom_content_candidate79,055
no_dns50,597
client_error40,186
unknown_live25,940
dns_only14,708
commercial_redirect11,949
blank_or_tiny_page11,519
parked_or_placeholder11,397
server_error4,862
casino_or_betting3,336
login_or_admin_page2,415
under_construction1,471
domain_for_sale1,049
app_or_tool_candidate886
ai_or_tech_candidate224
Landing categories
CategoryDomainsAvg score
thin_or_blank51,6800.97
business_or_project13,39578.45
summarizable_site10,96686.61
developer_or_docs9,12388.23
sludge_or_spam8,67063.14
unknown_landing7,60046.29
product_or_saas6,29493.15
content_or_blog4,40778.27
login_or_admin3,23217.82
extract_failed1,8970.0
non_html_asset1360.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.