No — openapi.casa is IPv4 only.

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

D
IPv6 readiness
The website has no IPv6.
Website over IPv6
openapi.casa 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
 Which outside scripts, fonts, payments or chat openapi.casa loads from have no IPv6.

What's keeping openapi.casa from an A

  1. Give openapi.casa 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
  2. 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

openapi.casa  IPv4 only

A (IPv4)38.87.116.229
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/3c0b3ELVFW · How we measure

Checked 2026-11-10 02:02:05 UTC. Full DNS report: dns.pizza/domain/openapi.casa · Age, certificate and blocklists: how.is/openapi.casa · JSON: /api/v1/openapi.casa