No — yayup.app is IPv4 only.

Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.

Measured 2026-11-04 16:30 UTC. We reuse a result for up to a week, so we aren't testing the same site over and over. Check yayup.app now

IPv6 readiness

The website has no IPv6.

Website over IPv6 yayup.app has no AAAA record.	no
www over IPv6 www.yayup.app has no AAAA record.	no
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. eforward1.registrar-servers.com ✗eforward2.registrar-servers.com ✗eforward3.registrar-servers.com ✗eforward4.registrar-servers.com ✗eforward5.registrar-servers.com ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. dns1.registrar-servers.com ✓dns2.registrar-servers.com ✓	yes

First measured 2026-11-04; last confirmed 2026-11-04.

What's keeping yayup.app from an A

Give yayup.app an IPv6 address
Ask your hosting provider for the site's IPv6 address (or the hostname to point at), then publish it as an AAAA record. If your host doesn't offer IPv6, a proxy that does can sit in front. How to add an AAAA record
www.yayup.app is hosted on Vercel, which has no IPv6
It points at cname.vercel-dns.com, and that name has no AAAA record — so nothing you add in your own DNS can give it IPv6. Put an IPv6-capable proxy in front (Cloudflare's proxied DNS does this), or host somewhere that offers IPv6. Which platforms offer IPv6
Mail servers without IPv6
eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com, eforward4.registrar-servers.com, eforward5.registrar-servers.com have no AAAA record, so mail from IPv6-only servers can't reach them directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.

Check again

yayup.app IPv4 only

A (IPv4)	76.76.21.21
AAAA (IPv6)	none

www.yayup.app IPv4 only

Alias of	cname.vercel-dns.com
A (IPv4)	76.76.21.241 66.33.60.193
AAAA (IPv6)	none

What this means

Visitors on IPv6-only networks (many mobile carriers) can still reach it, but only through a translator their carrier runs (NAT64). The site itself has no IPv6 address — and you can't make one up from the IPv4. Why some hosts don't offer it

Copy the evidence — a citation-ready record of this measurement

IPv6 measurement: yayup.app
Measured 2026-11-04 16:30:32 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    76.76.21.21
AAAA (IPv6): none
www AAAA:    none

Readiness grade D: The website has no IPv6.
- Website over IPv6: yayup.app has no AAAA record.
- www over IPv6: www.yayup.app has no AAAA record.
- Mail servers (MX) have IPv6: None of the mail servers has an AAAA record.
- Nameservers have IPv6: 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.

Reachability = a TCP connection opened on port 443 (or 80).
No TLS or HTTP request was made.
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/1ZprfeRfky

Permanent link: aaaa.bot/r/1ZprfeRfky · How we measure

Checked 2026-11-04 16:30:32 UTC. Full DNS report: dns.pizza/domain/yayup.app · Age, certificate and blocklists: how.is/yayup.app · JSON: /api/v1/yayup.app