reproductivehealthservices.gov
Updated:
2022-10-19 00:04:09 UTC (768 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- reproductivehealthservices.gov/A
- reproductivehealthservices.gov/NS
- reproductivehealthservices.gov/NSEC3PARAM
- reproductivehealthservices.gov/NSEC3PARAM
- reproductivehealthservices.gov/SOA
- reproductivehealthservices.gov/TXT
DNSKEY/DS/NSEC status
Secure (15)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 261)
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- reproductivehealthservices.gov/DNSKEY (alg 8, id 14520)
- reproductivehealthservices.gov/DNSKEY (alg 8, id 27535)
- reproductivehealthservices.gov/DNSKEY (alg 8, id 29850)
- reproductivehealthservices.gov/DNSKEY (alg 8, id 42450)
- reproductivehealthservices.gov/DNSKEY (alg 8, id 65089)
- reproductivehealthservices.gov/DS (alg 8, id 27535)
- reproductivehealthservices.gov/DS (alg 8, id 27535)
- reproductivehealthservices.gov/DS (alg 8, id 65089)
- reproductivehealthservices.gov/DS (alg 8, id 65089)
Delegation status
Secure (2)
- . to gov
- gov to reproductivehealthservices.gov
Notices
Errors (7)
- reproductivehealthservices.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f220:0:1::3a, 2607:f220:0:1::3b)
- reproductivehealthservices.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_NOEDNS_)
- reproductivehealthservices.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_NOEDNS_)
- reproductivehealthservices.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- 4ijyqz9d18.reproductivehealthservices.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- reproductivehealthservices.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- reproductivehealthservices.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
- reproductivehealthservices.gov/DS (alg 8, id 27535): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- reproductivehealthservices.gov/DS (alg 8, id 27535): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- reproductivehealthservices.gov/DS (alg 8, id 27535): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- reproductivehealthservices.gov/DS (alg 8, id 27535): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- reproductivehealthservices.gov/DS (alg 8, id 65089): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- reproductivehealthservices.gov/DS (alg 8, id 65089): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- reproductivehealthservices.gov/DS (alg 8, id 65089): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- reproductivehealthservices.gov/DS (alg 8, id 65089): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- reproductivehealthservices.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- 4ijyqz9d18.reproductivehealthservices.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- reproductivehealthservices.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- reproductivehealthservices.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
