Public status

Public website live. Owned domain connecting.

The Vercel production URL is the current working public website. The owned Yapify domains are attached in Vercel and wait on registrar DNS before launch.

Last live check: 27/06/2026, 9:33:56 pm · Deploy 2fd8511
Live1
DNS pending2
Observed pass3
Observed fail2
Runtimeproduction
Projectyapify-australia
Git refmain
Commit2fd8511
Public website fallback URL

Temporary Vercel fallback URL is live while the owned domain finishes DNS cutover.

Live
Observed passHTTP check: 200 https://yapify-public-web.vercel.app
https://yapify-public-web.vercel.app
Evidence
Public homepage route returns HTTP 200 Membership registration route returns HTTP 200 Vercel project is renamed to yapify-australia; old fallback alias still serves the current production deployment
Next action
Use yapify.co as the primary public URL after registrar DNS resolves.
Blocked claim
Do not present this fallback alias as the final owned public domain.
Owned domain

Connected in Vercel; waiting for registrar DNS.

DNS pending
Observed failDNS A record: 216.150.1.1 | Nameservers: dns2.registrar-servers.com, dns1.registrar-servers.com | HTTP check: 200 https://yapify.co
https://yapify.co
Evidence
Vercel domain is attached to the yapify-australia project Local DNS still returns no A record
Next action
Set A yapify.co 76.76.21.21 or delegate nameservers to ns1.vercel-dns.com and ns2.vercel-dns.com.
Blocked claim
Do not claim yapify.co is live until DNS and HTTPS checks pass.
WWW domain

Connected in Vercel; waiting for registrar DNS.

DNS pending
Observed failDNS A record: 216.150.1.1, 216.150.16.1 | Nameservers: dns1.registrar-servers.com, dns2.registrar-servers.com | HTTP check: 308 https://www.yapify.co
https://www.yapify.co
Evidence
Vercel domain is attached to the yapify-australia project Local DNS still returns no A record
Next action
Set A www.yapify.co 76.76.21.21 or delegate nameservers to ns1.vercel-dns.com and ns2.vercel-dns.com.
Blocked claim
Do not claim www.yapify.co is live until DNS and HTTPS checks pass.
Membership intake

Open for public applications; every submission goes to Command Centre review.

Review gated
Observed passHTTP check: 200 https://yapify-public-web.vercel.app/membership/register
https://yapify-public-web.vercel.app/membership/register
Evidence
Signed public-to-Command-Centre bridge is live Final live regression created public boundary, internal canonical, audit and attention evidence
Next action
Keep approval, cards, access and finance behind internal review.
Blocked claim
No public submission creates final membership, access or finance state automatically.
Command Centre

Private operating hub for reviewed work.

Private
Observed passHTTP check: 200 https://yapify-finance-platform.vercel.app/login | HTTP check: 307 https://yapify-finance-platform.vercel.app/platform/data-architecture
https://yapify-finance-platform.vercel.app/login
Evidence
Login route returns HTTP 200 Protected data architecture route redirects unauthenticated users to login
Next action
Keep Command Centre routes protected by login and role permissions.
Blocked claim
No public user access to internal Command Centre data.
Status endpoint/status/readiness
Open JSON readiness snapshot