Skip to the page

Issue 2026-09-19The machinery behind this issue

Methods · 2026-09-19

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-19
arrived
336,080
resolved DNS
276,252
answered
190,760
looked custom
91,745
extracted
118,806
judged
998
catalogued
982

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
Weird Finds615983.51
Personal Pages171783.41
Human Services151282.8
Content & Blogs787882.51
Developer Corner12111782.13
Oddly Specific343482.03
Civic & Public Life555481.62
Learning & Exams333381.61
Commerce Shelf292981.24
AI Table444381.23
Useful Tools44444180.73
Food, Events & Hospitality161679.69
Global Trade Desk131379.31
Local Businesses8877.88
Suspicious Gentlemen282875.86
Skip2040.5

05 · Before judging

Probe and landing classifications

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

Probe classifications
ClassificationDomains
custom_content_candidate78,661
client_error63,032
no_dns59,828
blank_or_tiny_page50,827
unknown_live27,200
dns_only15,538
commercial_redirect12,162
parked_or_placeholder11,679
server_error6,477
casino_or_betting5,105
login_or_admin_page2,463
under_construction1,690
app_or_tool_candidate725
domain_for_sale494
ai_or_tech_candidate197
unknown2
Landing categories
CategoryDomainsAvg score
thin_or_blank63,2140.79
business_or_project13,28976.89
summarizable_site8,66183.13
developer_or_docs7,72885.93
unknown_landing6,60346.49
product_or_saas5,07388.34
content_or_blog4,42676.66
sludge_or_spam4,15351.41
login_or_admin3,34422.26
extract_failed2,1640.0
non_html_asset1510.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.