Skip to the page

Issue 2026-09-03The machinery behind this issue

Methods · 2026-09-03

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-03
arrived
383,329
resolved DNS
315,227
answered
239,966
looked custom
110,216
extracted
140,211
judged
1,000
catalogued
999

04 · Public shelves

Editorial map

How judged candidates were distributed through the issue.

CategoryJudgedShownAverage interest
Personal Pages171784.82
Weird Finds555583.85
Civic & Public Life848482.07
Learning & Exams282881.79
Developer Corner10710781.73
Commerce Shelf282881.25
Content & Blogs10010080.67
Oddly Specific282880.57
Useful Tools43943980.52
Local Businesses101080.2
AI Table323280.03
Suspicious Gentlemen191979.16
Human Services6679.0
Food, Events & Hospitality303078.93
Global Trade Desk151578.13
So Bad It's Good1168.0
Skip105.0

05 · Before judging

Probe and landing classifications

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

Probe classifications
ClassificationDomains
custom_content_candidate96,424
blank_or_tiny_page74,440
no_dns68,102
client_error41,428
unknown_live31,169
dns_only26,645
commercial_redirect12,865
parked_or_placeholder12,213
casino_or_betting7,371
server_error6,771
login_or_admin_page2,553
under_construction1,981
app_or_tool_candidate647
domain_for_sale439
ai_or_tech_candidate280
unknown1
Landing categories
CategoryDomainsAvg score
thin_or_blank73,5200.69
business_or_project14,64476.26
product_or_saas8,85677.04
developer_or_docs8,19582.04
summarizable_site7,95082.1
extract_failed7,3220.0
unknown_landing6,84444.6
content_or_blog5,25076.25
sludge_or_spam4,77444.79
login_or_admin2,74516.32
non_html_asset1110.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.