No — zapcoder.cloud is IPv4 only.

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

This is a saved measurement from 2026-11-12 15:53 UTC. Check zapcoder.cloud live now

D
IPv6 readiness
The website has no IPv6.
Website over IPv6
zapcoder.cloud has no AAAA record.		no
www over IPv6
www.zapcoder.cloud has no AAAA record.		no
Mail servers (MX) have IPv6
Every mail server has an AAAA record.
mx2.hostinger.com ✓mx1.hostinger.com ✓
yes
Nameservers have IPv6
2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
solar.dns-parking.com ✓lunar.dns-parking.com ✓
yes

What's keeping zapcoder.cloud from an A

  1. Give zapcoder.cloud and www.zapcoder.cloud 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

Check again

zapcoder.cloud  IPv4 only

A (IPv4)179.236.240.151
AAAA (IPv6)none

www.zapcoder.cloud  IPv4 only

A (IPv4)179.236.240.151
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

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

Checked 2026-11-12 15:53:48 UTC. Full DNS report: dns.pizza/domain/zapcoder.cloud · Age, certificate and blocklists: how.is/zapcoder.cloud · JSON: /api/v1/zapcoder.cloud