healthcare.gov/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
sv7m0.qnso5.healthcare.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
healthcare.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
healthcare.gov/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (38)
RRSIG healthcare.gov/A alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/A alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/A alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/A alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/A alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/A alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/A alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/A alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/AAAA alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/AAAA alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/AAAA alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/AAAA alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/AAAA alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/AAAA alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/AAAA alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/AAAA alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/DNSKEY alg 7, id 15654: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/DNSKEY alg 7, id 15654: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/DNSKEY alg 7, id 15654: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/DNSKEY alg 7, id 15654: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/DNSKEY alg 7, id 17151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/DNSKEY alg 7, id 17151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/DNSKEY alg 7, id 17151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/DNSKEY alg 7, id 17151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/MX alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/NS alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/NSEC3PARAM alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/SOA alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG healthcare.gov/TXT alg 7, id 18558: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
healthcare.gov/DNSKEY (alg 7, id 15654): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::40, UDP_-_EDNS0_4096_D_KN)
healthcare.gov/DNSKEY (alg 7, id 17151): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::40, UDP_-_EDNS0_4096_D_KN)
healthcare.gov/DNSKEY (alg 7, id 18558): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::40, UDP_-_EDNS0_4096_D_KN)
healthcare.gov/DNSKEY (alg 7, id 59522): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::40, UDP_-_EDNS0_4096_D_KN)
healthcare.gov/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
healthcare.gov/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
healthcare.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
healthcare.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
sv7m0.qnso5.healthcare.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.