Domain Status — axomed.com.pk Connection Report

🌐 Where the domain stands right now

Verified with live DNS lookups (dig / DNS-over-HTTPS) and HTTP checks on 11 Aug 2026.

Apex (axomed.com.pk)

216.198.79.1

Amazon/AWS (parked or proxied)

www (www.axomed.com.pk)

Vercel (vercel-dns-017)

LIVE — HTTP 200

SSL Certificate

Let's Encrypt (valid)

Auto-renewed

Backend (api)

Not on domain yet

Needs CNAME

✅ Good news: the domain is connected and resolving — https://www.axomed.com.pk returns HTTP 200 with a valid Let's Encrypt SSL certificate. Someone (you) already pointed it at Vercel.

⚠️ But: what's currently serving at that URL is a different AxoMed build (a React app) — it renders a blank white page. The full AXOMED site you and I built together (v22, 30+ pages, portals, CRM) is not yet deployed there. This is the last step to make the domain show the real product.

🔍 What the DNS actually says (raw findings)

Record	Type	Value found	Meaning
`axomed.com.pk`	A	`216.198.79.1`	Amazon IP — apex parked/pointing at registrar default (not used for www)
`www.axomed.com.pk`	CNAME	`f73599257b34429c.vercel-dns-017.com`	✅ Points to Vercel — this is the live frontend host
`axomed.com.pk`	NS	(no explicit NS delegation found — registrar default)	DNS records are managed at the registrar (not custom NS)
`axomed.pk`	A / HTTP	HTTP 502 Bad Gateway	Separate domain — not working, ignore for now
`api.axomed.com.pk`	CNAME	not set	⚠️ Backend not connected to domain yet

📌 Plain words: your domain's www record is live on Vercel with working SSL. The frontend project on that Vercel account is a different build. We just need to point that Vercel project at our v22 frontend — or point the CNAME at a fresh Netlify deploy of v22. 15–20 minutes of work.

🧭 Final target URLs

Main site (final)

https://www.axomed.com.pk

Will serve AXOMED v22

Frontend backup (now)

https://static.teamily.ai/…/axomed_v22/index.html

Working today

Backend API (final)

https://api.axomed.com.pk

Needs CNAME + Railway

🚀 Step-by-step — finish connecting the frontend (choose ONE option)

Option A — Replace the Vercel project (recommended, ~10 min)

Since the domain already points to Vercel, the easiest path is to put our v22 site into that Vercel project. I've prepared a ready-to-deploy axomed-v22-deploy.zip — you just upload it.

Download the deploy package I prepared: axomed-v22-deploy.zip (all 30+ v22 HTML/CSS/JS/images, ready for static hosting).
Go to vercel.com → your project that is currently serving axomed.com.pk (the one with the blank React page).
Click Deployments → ⋯ → Redeploy OR create a new project: Add New → Project, choose Deploy without Git / upload folder, and upload the contents of the zip (index.html at the root).
Vercel auto-detects a static site — framework preset: Other. Click Deploy.
In Project → Settings → Domains, make sure axomed.com.pk and www.axomed.com.pk are attached (they already resolve here).
Wait 1–2 minutes — SSL is automatic (Let's Encrypt). Done — https://www.axomed.com.pk now shows the full AXOMED site. 🎉

Option B — Point the domain to Netlify instead (also ~10 min)

Go to netlify.com → Add new site → Deploy manually and drag in the axomed-v22-deploy.zip (or the folder).
Netlify gives you a URL like axomed-v22.netlify.app — verify it loads.
In Netlify: Domain settings → Add custom domain → axomed.com.pk (and www).
At your registrar (where you bought axomed.com.pk), open DNS and set exactly these records:

Type Name Value A @ 75.2.60.5 (Netlify load balancer) CNAME www axomed-v22.netlify.app

📌 If you use Option B, the existing www → vercel-dns-017 CNAME must be changed to the Netlify target (or the A record added at apex). DNS changes take 30 min – 48 h to fully propagate.

⚙️ Connect the backend API (Railway) to the domain

The backend (Node.js/Express, currently live at the sandbox proxy) should get its own subdomain so the site can call it from the real domain.

Open railway.com → your AXOMED backend project (the one deployed as axomed-backend-production.up.railway.app).
Go to Settings → Networking → Generate Domain → keep the generated domain, then under Custom Domains click Add Custom Domain and enter api.axomed.com.pk.
Railway will show you the CNAME record to add at your registrar:

Type Name Value CNAME api axomed-backend-production.up.railway.app

Add that record at your registrar's DNS panel, save, and wait for propagation.
Verify: open https://api.axomed.com.pk/api/health — you should see {"status":"ok","service":"AXOMED API",…}.

✅ Backend health right now (sandbox proxy): {"status":"ok","service":"AXOMED API","version":"v6","db":{"users":18,"leads":10,"orders":17,"assessments":7}} — the API is up and reachable; it just needs the api. CNAME to live on the domain.

🤝 What I need from you to finish (2 things)

Access to your Vercel account (or Netlify). I can't log into vercel.com myself — no credentials. If you give me deploy access (or just upload the zip I prepared to Vercel yourself), I'll verify everything end-to-end.
Registrar DNS panel access — only needed if you choose Option B (Netlify) or the api. backend record. If you stay on Vercel, the frontend DNS is already done.

⚠️ Honest note: I cannot claim the domain is "fully connected" until our v22 frontend is actually deployed to that Vercel project and I can verify it loads. Right now the domain is connected to a different (blank) build — the DNS part is done, the deploy part is not.

📦 Deploy package

Ready for you: documents/axomed-v22-deploy/axomed-v22-deploy.zip — contains the whole v22 site (index.html at root, css/, js/, images/, all pages). Upload it to Vercel or Netlify as described above.

Urdu: Domain ka DNS ab Vercel par laga hua hai aur SSL bhi chal raha hai — bas jo project wahan serve ho raha hai wo purani blank build hai. Upar diya zip upload karo (Vercel/Netlify) to 15 minute mein aapki asal site domain par aa jayegi. Backend ke liye api. CNAME add karna hoga.

Domain Connection Status