reproductivehealthservices.gov

Updated: 2022-08-26 13:36:36 UTC (823 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 20826)
NSEC3 proving non-existence of reproductivehealthservices.gov/A
gov/DNSKEY (alg 8, id 261)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)

NSEC3 proving non-existence of reproductivehealthservices.gov/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of reproductivehealthservices.gov/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.

./DNSKEY (alg 8, id 20326): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
./DNSKEY (alg 8, id 20826): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
NSEC3 proving non-existence of reproductivehealthservices.gov/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of reproductivehealthservices.gov/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.