inbake.com publishes IPv6 but doesn't answer on it.

Has both IPv4 (A) and IPv6 (AAAA) addresses.

F
IPv6 readiness
Publishes IPv6 but doesn't answer on it — worse than having none.
Website over IPv6
inbake.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2406:da00:ff00::ac1b:17f no answer✗ 2406:da00:ff00::ac1b:277 no answer✗ 2406:da00:ff00::ac1b:fe no answer
broken
Mail servers (MX) have IPv6
No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.		yes
Nameservers have IPv6
4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns-1271.awsdns-30.org ✓ns-1982.awsdns-55.co.uk ✓ns-774.awsdns-32.net ✓ns-82.awsdns-10.com ✓
yes
 Load inbake.com over IPv6 from up to six other places — a second opinion.

What's keeping inbake.com from an A

  1. Fix or remove the AAAA record for inbake.com
    Something published an IPv6 address but nothing answers on it, so IPv6 visitors wait for a timeout first. Either make the server listen on IPv6 (and allow ports 443/80 through its firewall), or delete the AAAA record until it does.

Check again

inbake.com  Has IPv6

A (IPv4)54.197.119.184
AAAA (IPv6)2406:da00:ff00::ac1b:17f
2406:da00:ff00::ac1b:277
2406:da00:ff00::ac1b:fe

Browsers on dual-stack networks will usually pick IPv6 here (the "Happy Eyeballs" algorithm races both and prefers v6).

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

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

Checked 2026-11-01 16:18:33 UTC. Full DNS report: dns.pizza/domain/inbake.com · JSON: /api/v1/inbake.com