meet.stuttgart.de publishes IPv6 but doesn't answer on it.

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

This is a saved measurement from 2026-11-15 17:20 UTC. Check meet.stuttgart.de live now

F
IPv6 readiness
Publishes IPv6 but doesn't answer on it — worse than having none.
Website over IPv6
meet.stuttgart.de has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2a01:4f8:1c0c:54ad::1 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
3 of 3 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns1.arcor-ip.de ✓ns2.arcor-ip.de ✓ns3.arcor-ip.de ✓
yes

What's keeping meet.stuttgart.de from an A

  1. Fix or remove the AAAA record for meet.stuttgart.de
    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

meet.stuttgart.de  Has IPv6

Alias ofmeet.stuttgart.sichere-videokonferenz.io
A (IPv4)168.119.234.176
AAAA (IPv6)2a01:4f8:1c0c:54ad::1

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

Checked 2026-11-15 17:20:32 UTC. Full DNS report: dns.pizza/domain/meet.stuttgart.de · Age, certificate and blocklists: how.is/meet.stuttgart.de · JSON: /api/v1/meet.stuttgart.de