Skip to the page

Issue 2026-09-17The machinery behind this issue

Methods · 2026-09-17

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-17
arrived
345,627
resolved DNS
282,018
answered
208,139
looked custom
112,936
extracted
142,410
judged
1,000
catalogued
999

04 · Public shelves

Editorial map

How judged candidates were distributed through the issue.

CategoryJudgedShownAverage interest
Weird Finds545484.06
Personal Pages151583.0
Human Services9983.0
Oddly Specific454582.42
Learning & Exams404082.33
Content & Blogs848482.08
Developer Corner11011081.67
Civic & Public Life898981.44
Useful Tools42642681.32
Commerce Shelf242480.83
AI Table373780.7
Global Trade Desk161679.88
Local Businesses151579.47
Food, Events & Hospitality181879.06
Suspicious Gentlemen171778.53
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_candidate97,586
no_dns63,609
client_error51,400
blank_or_tiny_page45,738
unknown_live30,180
dns_only15,671
commercial_redirect14,367
parked_or_placeholder9,146
server_error6,186
casino_or_betting5,887
login_or_admin_page2,449
under_construction1,792
app_or_tool_candidate749
domain_for_sale633
ai_or_tech_candidate234
Landing categories
CategoryDomainsAvg score
thin_or_blank85,9870.59
business_or_project14,76078.53
summarizable_site8,98082.46
developer_or_docs7,87684.19
unknown_landing6,60548.11
product_or_saas5,58290.15
content_or_blog4,70275.23
sludge_or_spam3,52452.39
login_or_admin2,20919.02
extract_failed2,0570.0
non_html_asset1280.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.