Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.
Measured 2026-11-07 05:23 UTC. We reuse a result for up to a week, so we aren't testing the same site over and over. Check 385fadez-booking.com now
| Website over IPv6 385fadez-booking.com has no AAAA record. | no |
| www over IPv6 www.385fadez-booking.com has no AAAA record. | no |
| Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has no AAAA record. | no |
| Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns2.checkdomain.de ✓ns.checkdomain.de ✓ | yes |
First measured 2026-11-07; last confirmed 2026-11-07.
385fadez-booking.com IPv4 only
| A (IPv4) | 216.198.79.1 |
|---|---|
| AAAA (IPv6) | none |
www.385fadez-booking.com IPv4 only
| Alias of | cname.vercel-dns.com |
|---|---|
| A (IPv4) | 66.33.60.34 76.76.21.164 |
| AAAA (IPv6) | none |
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
Permanent link: aaaa.bot/r/zaq7ugg13F · How we measure
Checked 2026-11-07 05:23:44 UTC. Full DNS report: dns.pizza/domain/385fadez-booking.com · Age, certificate and blocklists: how.is/385fadez-booking.com · JSON: /api/v1/385fadez-booking.com