iad.gov
Updated:
2020-04-07 15:03:30 UTC (1692 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 33853)
- ./DNSKEY (alg 8, id 48903)
- gov/DNSKEY (alg 8, id 36558)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- iad.gov/DS (alg 8, id 61415)
- iad.gov/DS (alg 8, id 6620)
Non_existent (2)
- iad.gov/DNSKEY (alg 8, id 61415)
- iad.gov/DNSKEY (alg 8, id 6620)
Delegation status
Bogus (1)
- gov to iad.gov
Secure (1)
- . to gov
Notices
Errors (16)
- gov to iad.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
- iad.gov zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (8.44.96.33)
- iad.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (8.44.96.34)
- iad.gov zone: There was an error resolving the following NS name(s) to address(es): bloodgem.iad.gov
- iad.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (8.44.96.33, UDP_-_NOEDNS_)
- iad.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (8.44.96.33, UDP_-_NOEDNS_)
- iad.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (8.44.96.33, UDP_-_EDNS0_512_D_K)
- iad.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (8.44.96.33, UDP_-_NOEDNS_)
- iad.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (8.44.96.33, UDP_-_EDNS0_512_D_K)
- iad.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (8.44.96.33, 8.44.96.34, UDP_-_NOEDNS_)
- iad.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (8.44.96.33, UDP_-_NOEDNS_)
- iad.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- iad.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- iad.gov/SOA has errors; select the "Denial of existence" DNSSEC option to see them.
- iad.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- tf16sx8rb3.iad.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): 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.
- gov/DS (alg 8, id 7698): 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.
- iad.gov/DS (alg 8, id 61415): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- iad.gov/DS (alg 8, id 61415): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- iad.gov/DS (alg 8, id 61415): 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.
- iad.gov/DS (alg 8, id 61415): 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.
JavaScript is required to make the graph below interactive.
