Skip to the page

Issue 2026-09-07The machinery behind this issue

Methods · 2026-09-07

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-07
arrived
278,515
resolved DNS
240,292
answered
186,806
looked custom
75,850
extracted
97,124
judged
1,000
catalogued
997

04 · Public shelves

Editorial map

How judged candidates were distributed through the issue.

CategoryJudgedShownAverage interest
Weird Finds818183.04
Developer Corner12512582.26
Personal Pages333382.18
Learning & Exams414182.05
Civic & Public Life616181.79
AI Table272781.48
Content & Blogs818181.33
Human Services9981.22
Commerce Shelf343481.18
Oddly Specific383880.79
Useful Tools39739780.77
Food, Events & Hospitality191980.16
Local Businesses202079.3
Suspicious Gentlemen161677.69
Global Trade Desk151577.53
Still Interesting, But Barely1057.0
Skip2045.0

05 · Before judging

Probe and landing classifications

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

Probe classifications
ClassificationDomains
custom_content_candidate64,759
blank_or_tiny_page61,259
no_dns38,223
client_error35,000
unknown_live22,963
parked_or_placeholder18,818
dns_only13,997
commercial_redirect10,412
casino_or_betting5,087
server_error4,135
login_or_admin_page1,886
under_construction937
app_or_tool_candidate469
domain_for_sale358
ai_or_tech_candidate210
unknown2
Landing categories
CategoryDomainsAvg score
thin_or_blank51,3020.65
business_or_project13,47979.14
unknown_landing6,10144.46
summarizable_site5,92082.72
developer_or_docs5,03182.5
extract_failed3,8230.0
sludge_or_spam3,57242.65
product_or_saas3,22488.1
content_or_blog3,02572.61
login_or_admin1,52218.31
non_html_asset1250.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.