Skip to the page

Issue 2026-09-14The machinery behind this issue

Methods · 2026-09-14

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-14
arrived
263,868
resolved DNS
224,063
answered
173,179
looked custom
70,041
extracted
89,709
judged
1,000
catalogued
996

04 · Public shelves

Editorial map

How judged candidates were distributed through the issue.

CategoryJudgedShownAverage interest
Weird Finds787883.0
Learning & Exams363682.53
Content & Blogs969682.39
Civic & Public Life818182.27
Developer Corner13013082.13
Human Services131381.77
Personal Pages303081.57
Commerce Shelf282881.43
Food, Events & Hospitality101081.3
Local Businesses131381.08
Useful Tools36936981.04
AI Table313180.74
Oddly Specific424280.33
Global Trade Desk7779.57
Suspicious Gentlemen323277.53
Still Interesting, But Barely1067.0
Template Sludge1042.0
Skip2038.5

05 · Before judging

Probe and landing classifications

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

Probe classifications
ClassificationDomains
blank_or_tiny_page60,596
custom_content_candidate58,331
no_dns39,805
client_error34,467
unknown_live20,823
parked_or_placeholder15,491
dns_only12,512
commercial_redirect11,133
server_error3,669
casino_or_betting3,396
login_or_admin_page1,864
under_construction940
app_or_tool_candidate446
domain_for_sale264
ai_or_tech_candidate131
Landing categories
CategoryDomainsAvg score
thin_or_blank50,1590.69
business_or_project12,59376.81
summarizable_site5,59883.91
unknown_landing5,04446.74
developer_or_docs4,96783.96
product_or_saas3,05087.58
content_or_blog2,95475.31
sludge_or_spam2,37247.81
login_or_admin1,49719.42
extract_failed1,3960.0
non_html_asset790.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.