Landing page: fix the four broken-link references (status.zeroauth.dev x2 + api.zeroauth.dev x2)#32
Merged
Merged
Conversation
Audit found two unresolved subdomains being linked from public/index.html: - **status.zeroauth.dev** (2 spots) — footer brand-column "All systems operational" pill + the footer social-icons-row Status link. Subdomain DNS doesn't resolve. Repointed both to /api/health which is a real endpoint that returns API + Postgres + Redis + Base Sepolia health as JSON. Kept the "All systems operational" copy because the underlying health check is real; added a title tooltip noting that a dedicated status.zeroauth.dev page is on the roadmap. - **api.zeroauth.dev** (2 spots) — both Quickstart curl examples in the code-tabs section pointed at https://api.zeroauth.dev/v1/... The subdomain doesn't resolve. The canonical API URL is https://zeroauth.dev/v1/... (apex domain, no subdomain). Updated both curl examples accordingly so a developer copy-pasting them gets a 401 (auth required) instead of DNS-refused. Smoke-probed all 18 clickable hrefs after the edits — all return 200 (the two 404s in the smoke output are <link rel="preconnect"> hints to fonts.googleapis.com / fonts.gstatic.com root URLs; the actual font CSS request /css2?family=Inter... 200s correctly, and those preconnect URLs are correct standard behaviour, not user-facing links). Cross-repo sweep clean: no api.zeroauth.dev or status.zeroauth.dev refs left in docs/, dashboard/, or website/ (Docusaurus source). The governance repo's incident-response.md still mentions status.zeroauth.dev intentionally — flagged there as "planned, not yet wired up" rather than as a live URL. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Replaces four broken links on the landing page that pointed to unresolved subdomains (status.zeroauth.dev, api.zeroauth.dev) with working alternatives on the apex domain.
Changes:
- Footer "All systems operational" pill and footer Status icon now link to
/api/healthinstead ofstatus.zeroauth.dev. - Quickstart curl examples now target
https://zeroauth.dev/v1/...instead ofapi.zeroauth.dev/v1/.... - Updated
aria-labelon the status icon from "Status" to "Health" and added atitletooltip explaining the interim health endpoint.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
pulkitpareek18
added a commit
that referenced
this pull request
May 15, 2026
Audit found two unresolved subdomains being linked from public/index.html: - **status.zeroauth.dev** (2 spots) — footer brand-column "All systems operational" pill + the footer social-icons-row Status link. Subdomain DNS doesn't resolve. Repointed both to /api/health which is a real endpoint that returns API + Postgres + Redis + Base Sepolia health as JSON. Kept the "All systems operational" copy because the underlying health check is real; added a title tooltip noting that a dedicated status.zeroauth.dev page is on the roadmap. - **api.zeroauth.dev** (2 spots) — both Quickstart curl examples in the code-tabs section pointed at https://api.zeroauth.dev/v1/... The subdomain doesn't resolve. The canonical API URL is https://zeroauth.dev/v1/... (apex domain, no subdomain). Updated both curl examples accordingly so a developer copy-pasting them gets a 401 (auth required) instead of DNS-refused. Smoke-probed all 18 clickable hrefs after the edits — all return 200 (the two 404s in the smoke output are <link rel="preconnect"> hints to fonts.googleapis.com / fonts.gstatic.com root URLs; the actual font CSS request /css2?family=Inter... 200s correctly, and those preconnect URLs are correct standard behaviour, not user-facing links). Cross-repo sweep clean: no api.zeroauth.dev or status.zeroauth.dev refs left in docs/, dashboard/, or website/ (Docusaurus source). The governance repo's incident-response.md still mentions status.zeroauth.dev intentionally — flagged there as "planned, not yet wired up" rather than as a live URL.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You spotted `status.zeroauth.dev`. Audit found three more in the same class.
What was broken
Probed every clickable href on the landing page. Two unresolved subdomains:
The Quickstart fix matters most — anyone copy-pasting those curl commands was getting a DNS error instead of an API response. Now they'll get a real 401 (auth required), which is the expected first-touch experience.
Verification
Smoke-probed every clickable href after the edits:
```
200 /api/health
200 /dashboard/login
200 /dashboard/signup
200 /demo.html
200 /docs
200 /docs/getting-started/quickstart/
200 /docs/reference/api-reference
200 /docs/whitepaper.pdf
200 /favicon.svg
200 https://github.com/pulkitpareek18/ZeroAuth
200 https://github.com/pulkitpareek18/ZeroAuth/blob/main/CODE_OF_CONDUCT.md
200 https://github.com/pulkitpareek18/ZeroAuth/blob/main/CONTRIBUTING.md
200 https://github.com/pulkitpareek18/ZeroAuth/blob/main/LICENSE
200 https://github.com/pulkitpareek18/ZeroAuth/blob/main/SECURITY.md
200 https://github.com/pulkitpareek18/ZeroAuth/issues
```
(`https://fonts.googleapis.com\` and `https://fonts.gstatic.com\` 404 on the root URL but they're `` hints, not user-facing links — the actual font CSS request returns 200.)
Cross-repo sweep
No `api.zeroauth.dev` or `status.zeroauth.dev` references left in `docs/`, `dashboard/`, or `website/`. The governance repo's `incident-response.md` keeps a single mention of `status.zeroauth.dev` but it's flagged there as "planned — status page not yet wired up", which is the correct framing for a runbook.
Out of scope
🤖 Generated with Claude Code