Local Grid Network · part of The Local Internet
WHAT MAKES UP THE LOCAL GRID NETWORK?
The Local Grid is organized, not a pile of unrelated addresses. A destination belongs to a place, to an experience family, or to a subject — and this page shows those relationships as the system actually holds them.
The relationships connecting destinations across The Local Internet.
What makes up the Local Grid network?
Every relationship below is read from an existing registry when this page renders. Nothing here is a hand-maintained domain list, and a relationship that the system does not hold is not drawn.
THE GEOGRAPHIC NETWORK
Read top to bottom. Each tier exists because the system registers destinations for it.
- THE LOCAL INTERNET
One shared system of records, geography and governance behind every destination.
- STATES50
Each state that has at least one registered destination, across the experience families below.
- STATE DESTINATIONS249
Place × experience: one state paired with one registered experience family is one destination.
This is the one shared geographic model, not a second geographic tree. A state appears because a destination is registered for it, never because a name exists.
CHOOSE A NETWORK
Each experience family is its own network of destinations across the states. Choose one to see where it reaches, then follow a relationship to the actual experience.
IZ family
Find businesses, places and local information.
- AlabamaizAlabama
- AlaskaizAlaska
- ArizonaizArizona
- ArkansasizArkansas
- CaliforniaizCalifornia
- ColoradoizColorado
- ConnecticutizConnecticut
- DelawareizDelaware
- FloridaizFlorida
- GeorgiaizGeorgia
- HawaiiizHawaii
- IllinoisizIllinois
- IndianaizIndiana
- IowaizIowa
- KansasizKansas
- KentuckyizKentucky
- LouisianaizLouisiana
- MaineizMaine
- MarylandizMaryland
- MassachusettsizMassachusetts
- MichiganizMichigan
- MinnesotaizMinnesota
- MississippiizMississippi
- MissouriizMissouri
- MontanaizMontana
- NebraskaizNebraska
- NevadaizNevada
- New HampshireizNew Hampshire
- New JerseyizNew Jersey
- New MexicoizNew Mexico
- New YorkizNew York
- North CarolinaizNorth Carolina
- North DakotaizNorth Dakota
- OhioizOhio
- OklahomaizOklahoma
- OregonizOregon
- PennsylvaniaizPennsylvania
- Rhode IslandizRhode Island
- South CarolinaizSouth Carolina
- South DakotaizSouth Dakota
- TennesseeizTennessee
- TexasizTexas
- UtahizUtah
- VermontizVermont
- VirginiaizVirginia
- WashingtonizWashington
- West VirginiaizWest Virginia
- WisconsinizWisconsin
- WyomingizWyoming
A group exists here only because the system registers destinations for it. Marketplace is one of those families — it is a registered experience family, not a count of marketplace nodes.
FOLLOW ONE PLACE
One state, and every experience registered for it. This is the relationship the system holds: a place paired with an experience becomes a destination.
- AlabamaizDiscover
Find businesses, places and local information.
- AlabamaizzMedia
Explore state information, stories and media.
- AlabamaizzeParticipate
Contribute, engage and participate locally.
- AlabamazzMarketplace
Browse listings and marketplace opportunities.
- The Alabama SurfaceSurface
Explore structured information about businesses, places and organizations across the state.
NETWORKS BY SUBJECT
Not every destination sits in the geographic hierarchy. A subject destination relates to the network by what it is about, reading the same records and the same geography.
BUSINESS AND OPPORTUNITY
3BUSINESS VERTICALS
9CATEGORY VERTICALS
10CONSUMER DISCOVERY
4HOME AND PROPERTY
8INFORMATION AND COMMUNITY
5OBJECT AND INTENT SURFACES
7PEOPLE AND LIFESTYLE
4PLACES, ACTIVITIES AND EXPERIENCES
4WHAT THE NETWORK MEASURES
397
DISTINCT EXPERIENCES
Experiences this application serves. Several addresses can reach one experience.
402
ADDRESSES SERVED
Apex hostnames the resolver answers for. Not a count of owned names.
5
EXPERIENCE FAMILIES
Registered state experience families, each with destinations of its own.
249
STATE DESTINATIONS
Place × experience pairs registered across the states.
54
SUBJECT DESTINATIONS
Destinations that relate by subject or intent rather than by geography.
284
CONFIGURED DESTINATIONS
Rows in the Surface Registry — places an object can legitimately be published to.
Each figure is counted from the running system when this page rendered and says what it counts. Owned name, configured destination, address served and distinct experience are four different measurements, and none of them is a DNS check: registrar and DNS state is held outside the system and is never inferred here.
- OWNED NAME
- A domain held. Not shown here, and never counted as participation.
- CONFIGURED DESTINATION
- A registry row a record can legitimately be published to.
- ADDRESS SERVED
- A hostname this application answers for.
- DISTINCT EXPERIENCE
- One experience, however many addresses reach it.
- DNS-VERIFIED DOMAIN
- Not measured by this system. Never claimed and never inferred.
ADDRESSES INTO THIS PAGE
localgridnetwork.com · www.localgridnetwork.com
An address is not a destination. Several addresses can reach one experience, and the experience is counted once.
ONE QUESTION EACH
- LOCAL GRID NETWORKWhat makes up the Local Grid network?
- ONE LOCAL GRIDWhat is connected?Open
- THE LOCAL GRIDHow does the Grid fit together?Open
- THE LOCAL SURFACESWhat user-facing experiences exist?Open
- THE LOCAL INTERNET STACKWhat layers make the system work?Open
- THE NAMESPACE COMPANYWhat names exist and what roles do they represent?Open
- THE LOCAL INTERNETWhat is the overall ecosystem?Open
Explore all Local Surfaces → TheLocalSurfaces.comThe Network shows relationships. The Surfaces catalog shows every experience.
WHAT THIS PAGE IS NOT
- A DOMAIN PORTFOLIO
- Owning a name is not participating in the network. Only destinations the application actually serves appear here.
- A SECOND REGISTRY
- No destination, geography or classification is defined on this page. It reads the ones that already exist.
- A CATALOG OF EXPERIENCES
- That is TheLocalSurfaces. This page shows how destinations relate, not what each one offers.
- A SEARCH ENGINE
- You can follow a relationship to a real destination. There is nothing to query here.
An authoritative object may legitimately appear on several destinations. Which URL should be canonical for indexing is still an open policy question, and the Network does not decide it.