tmdbhouse.gov
Updated:
2021-03-18 10:26:56 UTC (1348 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- tmdbhouse.gov/NS
- tmdbhouse.gov/SOA
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- gov/DNSKEY (alg 8, id 27306)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- tmdbhouse.gov/DNSKEY (alg 13, id 542)
- tmdbhouse.gov/DNSKEY (alg 13, id 63035)
- tmdbhouse.gov/DS (alg 13, id 542)
- tmdbhouse.gov/DS (alg 13, id 542)
Delegation status
Secure (2)
- . to gov
- gov to tmdbhouse.gov
Notices
Warnings (5)
- gov to tmdbhouse.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): oxygen2.house.gov See RFC 1034, Sec. 4.2.2.
- tmdbhouse.gov/DS (alg 13, id 542): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- tmdbhouse.gov/DS (alg 13, id 542): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- tmdbhouse.gov/DS (alg 13, id 542): 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.
- tmdbhouse.gov/DS (alg 13, id 542): 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.
