About Beta Directory

What this directory is

Beta Directory is an independent index of public websites. Each profile combines a plain-language explanation of the product, organization, publication, or project represented by a domain with dated technical observations. The aim is to answer two different questions without mixing them: what the subject is, and what public systems returned when the domain was checked.

Beta Directory is not owned by, endorsed by, or affiliated with the websites it lists. A listing is not an award, recommendation, partnership, or paid certification.

Where editorial information comes from

Editors begin with the question a visitor is likely to ask, such as “What is Astro about?” Claims are researched from primary and authoritative sources. These can include an organization’s official website and documentation, maintained project repositories, standards bodies, regulators, registry operators, and current corporate filings. Every domain article lists the sources used so a reader can inspect them directly.

A public repository is used only when it answers a relevant product or project question. Implementation details that do not help a visitor understand the subject are left out of the article.

Where technical records come from

• Public DNS-over-HTTPS queries collect the record types the directory checks, including A, AAAA, CNAME, MX, NS, TXT, CAA, SOA, SRV, HTTPS, SVCB, NAPTR, DS, and DNSKEY when the domain publishes an answer.
• RDAP services operated by registries and registrars provide registration events, registrar details, domain statuses, and nameservers when those fields are public.
• HTTP and TLS checks record the response, redirects, latency, certificate details, response headers, and visible page signals at a particular time.
• Cloudflare's public domain and page-scan data provide dated popularity ranges, categories, outgoing links, requested hostnames, IP addresses, and network numbers when available.
• Favicons are loaded for link recognition. Page images are captured on the local publishing machine with Playwright, uploaded to Cloudflare R2, and served from a public asset hostname.

Cloudflare D1 is the publication source of truth. A scheduled production build exports approved records and prerenders them as static HTML, so normal page views do not repeat upstream requests or run database queries.

Limits of the evidence

A profile is a snapshot, not continuous monitoring. HTTP 200 means one request succeeded; it does not guarantee future uptime or that every route works. A valid certificate secures a connection; it does not certify the truth or safety of the content. Technology detection uses public signals and can be incomplete. A DNS response shows the records returned for the queried name and type, not a private copy of the domain owner’s entire DNS zone.

Popularity data can be an exact position or a broader range depending on the provider’s result. Shared network addresses do not reveal a private origin server. Registry details may be redacted, unavailable, or delayed. The page shows observation dates so readers can decide whether a record is fresh enough for their purpose.

Editorial and translation policy

English is the editorial source of truth. English research and human review are completed before translation starts. Other languages are faithful translations of the approved English fields; they are not separately researched articles and cannot add new claims. URLs, measurements, uncertainty, headings, and citation meaning are preserved. Missing facts remain missing.

Status, registration, DNS, TLS, technology, and network views favor labeled evidence over generated prose. This keeps changing measurements separate from the explanatory article and reduces the risk of turning an inference into a fact.

Publication and refreshes

Imported domains begin as drafts. A profile is published only after its English article, citations, structured evidence, translations, links, image, metadata, and quality checks pass the publication checklist. Publishing is scheduled locally rather than delegated to an unattended writing API.

A refresh requests newer public evidence and stores another dated observation. It does not silently rewrite an old measurement to look current. Refreshes can be rate-limited, and an upstream service may be temporarily unavailable.

Corrections and accountability

Websites and public records change. If a profile is inaccurate, attributes a domain incorrectly, or exposes personal information that should be reviewed, email contact@beta.directory. Include the domain, disputed field, your relationship to it, and a primary source or other evidence. We review the request and preserve accurate timestamps rather than making historical observations appear current.