Skip to the page

Issue 2026-11-17The machinery behind this issue

Methods · 2026-11-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-11-17
arrived
300,778
resolved DNS
220,782
answered
130,158
looked custom
78,435
extracted
101,455
judged
1,000
catalogued
976

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 Finds747379.43
Food, Events & Hospitality7779.43
Civic & Public Life827878.96
Personal Pages232378.91
Developer Corner777778.84
Human Services111178.73
AI Table252278.6
Content & Blogs868378.4
Learning & Exams616178.38
Useful Tools45144577.99
Global Trade Desk7777.71
Local Businesses101077.6
Commerce Shelf252176.96
Oddly Specific363676.94
Suspicious Gentlemen222270.68
Skip3012.67

05 · Before judging

Probe and landing classifications

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

Probe classifications
ClassificationDomains
no_dns79,996
client_error71,598
custom_content_candidate68,799
unknown_live25,624
dns_only14,080
parked_or_placeholder10,710
blank_or_tiny_page9,188
commercial_redirect8,654
server_error4,817
casino_or_betting3,323
login_or_admin_page1,756
under_construction1,080
app_or_tool_candidate819
domain_for_sale171
ai_or_tech_candidate163
Landing categories
CategoryDomainsAvg score
thin_or_blank46,3840.64
business_or_project10,60479.75
product_or_saas10,16074.47
summarizable_site8,38584.36
developer_or_docs6,83787.85
unknown_landing6,29245.05
sludge_or_spam4,20557.15
content_or_blog3,78278.19
login_or_admin2,49817.22
extract_failed2,1780.0
non_html_asset1300.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.