beta.census.gov publishes IPv6 but doesn't answer on it.

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

Measured 2026-11-01 21:56 UTC. We reuse a result for up to a week, so we aren't testing the same site over and over. Check beta.census.gov now

F
IPv6 readiness
Publishes IPv6 but doesn't answer on it — worse than having none.
Website over IPv6
beta.census.gov has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2610:20:2010:a05:1000:0:9481:4baa 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
2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns1e.census.gov ✓ns2e.census.gov ✓
yes

This is from one location so far. We confirm broken results from other continents; that hasn't finished yet.

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

 Load beta.census.gov over IPv6 from up to six other places — a second opinion.

What's keeping beta.census.gov from an A

  1. Fix or remove the AAAA record for beta.census.gov
    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

beta.census.gov  Has IPv6

A (IPv4)148.129.75.170
AAAA (IPv6)2610:20:2010:a05:1000:0:9481:4baa

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/Eqi6sxLIbL · How we measure

Checked 2026-11-01 21:56:10 UTC. Full DNS report: dns.pizza/domain/beta.census.gov · JSON: /api/v1/beta.census.gov