{"kind":"host","input":"getcited1.tech","report":{"host":"getcited1.tech","checkedAt":"2026-11-08T09:44:05.554Z","a":{"status":"found","values":["75.2.60.5"],"ttl":60,"via":"Cloudflare","cname":[]},"aaaa":{"status":"absent","via":"Cloudflare","cname":[]},"verdict":"ipv4-only","www":{"host":"www.getcited1.tech","a":{"status":"found","values":["98.84.224.111","18.208.88.157"],"ttl":60,"via":"Cloudflare","cname":["jade-meringue-c02239.netlify.app"]},"aaaa":{"status":"found","values":["2600:1f18:16e:df01::258","2600:1f18:16e:df01::259"],"ttl":60,"via":"Cloudflare","cname":["jade-meringue-c02239.netlify.app"]},"verdict":"dual-stack"}},"readiness":{"grade":"F","summary":"The www address publishes IPv6 but doesn't answer on it — worse than having none.","reachabilityTested":true,"checks":[{"key":"web","label":"Website over IPv6","status":"fail","detail":"getcited1.tech has no AAAA record."},{"key":"www","label":"www over IPv6","status":"broken","detail":"www.getcited1.tech 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":"2600:1f18:16e:df01::258","result":"no answer"},{"address":"2600:1f18:16e:df01::259","result":"no answer"}]},{"key":"mail","label":"Mail servers (MX) have IPv6","status":"fail","detail":"No MX records, so mail goes to the domain's own address (implicit MX). It has no AAAA record."},{"key":"dns","label":"Nameservers have IPv6","status":"pass","detail":"4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.","hosts":[{"host":"ns2.dns.host","ipv6":true},{"host":"ns4.dns.host","ipv6":true},{"host":"ns1.dns.host","ipv6":true},{"host":"ns3.dns.host","ipv6":true}]}]},"receiptId":"hRhKm76vnT","reused":true,"measuredAt":"2026-11-08T09:44:11.558Z"}