Skip to the page

Issue 2026-11-20The machinery behind this issue

Methods · 2026-11-20

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-20
arrived
386,049
resolved DNS
301,245
answered
187,506
looked custom
113,926
extracted
146,473
judged
1,000
catalogued
972

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
Personal Pages191981.21
Weird Finds585881.16
Civic & Public Life898080.84
Content & Blogs737280.16
Human Services131379.31
Developer Corner827979.3
Food, Events & Hospitality131379.08
Oddly Specific303078.67
Learning & Exams555578.51
Commerce Shelf292878.41
AI Table191878.16
Useful Tools48447578.03
Local Businesses131277.54
Global Trade Desk2276.5
Suspicious Gentlemen211874.43

05 · Before judging

Probe and landing classifications

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

Probe classifications
ClassificationDomains
custom_content_candidate99,084
no_dns84,804
client_error71,762
unknown_live34,675
dns_only33,064
parked_or_placeholder15,195
commercial_redirect13,580
blank_or_tiny_page13,053
server_error7,868
casino_or_betting5,934
login_or_admin_page2,926
under_construction1,763
domain_for_sale1,079
app_or_tool_candidate1,033
ai_or_tech_candidate229
Landing categories
CategoryDomainsAvg score
thin_or_blank65,1980.7
business_or_project17,16678.77
summarizable_site12,98085.37
product_or_saas11,61281.91
developer_or_docs10,54388.74
unknown_landing9,35745.15
sludge_or_spam7,53359.18
content_or_blog5,95678.19
login_or_admin3,76416.13
extract_failed2,1490.0
non_html_asset2150.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.