Something went wrong. Try again.
Monorepo for Aesthetic.Computer aesthetic.computer
Something went wrong. Try again.
Markdown
Cloudflare DNS Status #
Last audited: 2026-03-30
This file reflects the live Cloudflare state after the lith cutover.
The primary frontend origin is 209.38.133.33.
Frontend Records On lith #
aesthetic.computerzone:aesthetic.computer,api,bills,data,feed,give,keeps,l5,news,p5,pals,papers,processing,sitemap,wwwdata(A → 209.38.133.33, proxied) added 2026-06-29 — Linked Open Data / CIDOC CRM endpoint (crm.mjs); needs lith deploy to serve.
false.workzone:builds.false.workjas.lifezone:jas.lifejustanothersystem.orgzone:justanothersystem.org,wwwkidlisp.comzone:kidlisp.com,www,buy,calm,device,keep,keeps,learn,pj,topnotepat.comzone:notepat.com,wwwprompt.aczone:prompt.ac,api,l5,p5,papers,processing,sitemapwwwMISSING as of 2026-07-06 — falls into the*.prompt.ac → 100::Worker wildcard and 522s. Fix: addwwwA → 209.38.133.33 (proxied); Caddyfile already has the www→apex redirect.
quiltnet.orgzone:quiltnet.org,wwwsotce.netzone:sotce.net,www
Other Live Exceptions #
aesthetic.computerkeeps its non-lith service records for PDS, session, silo, oven, spaces/CDN, Auth0, Shopify, Stripe, and Cloudflare Worker endpoints.prompt.ackeeps*.prompt.ac -> 100::for the Worker wildcard.prompt.aczone ruleset "prompt.ac bare-domain auto-redirect" (dynamic redirect, ruleset 99ad241726fe48ee9db29ba97f11ad4d) was DISABLED 2026-09-01: it 301'd every non-root path to aesthetic.computer at the edge, which now belongs to lith's resolver (server.mjs serves the HTML prompt shell for dotless piece paths, 302s live wg codes, 301s dotted paths). Re-enable it only if the shell has to be pulled — it supersedes the origin's routing.sotce.netkeepschat.sotce.net -> 157.245.134.225plus its mail/Auth0 records.
Netlify Status #
- No production records in the audited zones point to
aesthetic-computer.netlify.app. - No production records in the audited zones point to
75.2.60.5. - Legacy
duckweedtri.aesthetic.computerandduckweedtri.prompt.acwere stale Netlify 404s during the audit and should resolve through lith-managed redirects instead.
Amail Inbound (added 2026-09-13) #
inbound.aesthetic.computerA → 209.38.133.33, DNS-only (Cloudflare does not proxy SMTP). This is the "route to host" target of the Google Workspace default-routing rule that catches unknown@aesthetic.computeraddresses;lith/mail-inbound.mjs(lith-mail.service, :25) files them as Amail. Caddy serves the same name over HTTPS only to hold its STARTTLS certificate.- The apex MX stays on Google (
aspmx.l.google.comet al.) — one human mailbox,mail@aesthetic.computer, lives there. - Mail authentication for the apex (added 2026-09-14 — there was none before,
so every
mail@aesthetic.computersend had been unauthenticated):aesthetic.computer TXT "v=spf1 include:_spf.google.com ~all"andgoogle._domainkey.aesthetic.computer TXT "v=DKIM1; …"(key generated in Admin → Gmail → Authenticate email; status "Authenticating email with DKIM"). DMARC staysp=nonefor now.