tmdbhouse.gov
Updated:
2020-10-09 13:07:58 UTC (1511 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (2)
- tmdbhouse.gov/NS
- tmdbhouse.gov/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- ./DNSKEY (alg 8, id 46594)
- gov/DNSKEY (alg 8, id 26665)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- tmdbhouse.gov/DS (alg 8, id 11149)
Non_existent (1)
- tmdbhouse.gov/DNSKEY (alg 8, id 11149)
Delegation status
Bogus (1)
- gov to tmdbhouse.gov
Secure (1)
- . to gov
Notices
Errors (12)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_K)
- gov to tmdbhouse.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. (156.154.64.109, 156.154.65.109, 156.154.66.109, 156.154.67.109, 216.218.141.197, 2001:502:4612::91, 2001:502:f3ff::91, 2610:a1:1014::91, 2610:a1:1015::91, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- gov to tmdbhouse.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (156.154.64.109, 156.154.65.109, 156.154.66.109, 156.154.67.109, 216.218.141.197, 2001:502:4612::91, 2001:502:f3ff::91, 2610:a1:1014::91, 2610:a1:1015::91, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- tmdbhouse.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.64.109, 156.154.65.109, 156.154.66.109, 156.154.67.109, 216.218.141.197, 2001:502:4612::91, 2001:502:f3ff::91, 2610:a1:1014::91, 2610:a1:1015::91, UDP_-_EDNS0_4096_D_K)
- tmdbhouse.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.64.109, 156.154.65.109, 156.154.66.109, 156.154.67.109, 216.218.141.197, 2001:502:4612::91, 2001:502:f3ff::91, 2610:a1:1014::91, 2610:a1:1015::91, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- tmdbhouse.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- boeva2fnug.tmdbhouse.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- tmdbhouse.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- tmdbhouse.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- tmdbhouse.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
- tmdbhouse.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- tmdbhouse.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- 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.
JavaScript is required to make the graph below interactive.
