{"kind":"host","input":"meet.stuttgart.de","report":{"host":"meet.stuttgart.de","checkedAt":"2026-11-15T17:20:32.872Z","a":{"status":"found","values":["168.119.234.176"],"ttl":600,"via":"Cloudflare","cname":["meet.stuttgart.sichere-videokonferenz.io"]},"aaaa":{"status":"found","values":["2a01:4f8:1c0c:54ad::1"],"ttl":600,"via":"Cloudflare","cname":["meet.stuttgart.sichere-videokonferenz.io"]},"verdict":"dual-stack"},"readiness":{"grade":"F","summary":"Publishes IPv6 but doesn't answer on it — worse than having none.","reachabilityTested":true,"checks":[{"key":"web","label":"Website over IPv6","status":"broken","detail":"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.","addresses":[{"address":"2a01:4f8:1c0c:54ad::1","result":"no answer"}]},{"key":"mail","label":"Mail servers (MX) have IPv6","status":"pass","detail":"No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record."},{"key":"dns","label":"Nameservers have IPv6","status":"pass","detail":"3 of 3 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.","hosts":[{"host":"ns1.arcor-ip.de","ipv6":true},{"host":"ns2.arcor-ip.de","ipv6":true},{"host":"ns3.arcor-ip.de","ipv6":true}]}]},"receiptId":"0vSnDhRz7Z","reused":true,"measuredAt":"2026-11-15T17:20:38.876Z"}