qtbam3if4l.taaps.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
taaps.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (18)
RRSIG taaps.gov/DNSKEY alg 8, id 30760: The value of the Signature Inception field of the RRSIG RR (2020-11-17 04:04:50+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-17 04:04:50+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG taaps.gov/DNSKEY alg 8, id 30760: The value of the Signature Inception field of the RRSIG RR (2020-11-17 04:04:50+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-17 04:04:50+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG taaps.gov/DNSKEY alg 8, id 64443: The value of the Signature Inception field of the RRSIG RR (2020-11-17 04:04:50+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-17 04:04:50+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG taaps.gov/DNSKEY alg 8, id 64443: The value of the Signature Inception field of the RRSIG RR (2020-11-17 04:04:50+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-17 04:04:50+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG taaps.gov/MX alg 8, id 64443: The value of the Signature Inception field of the RRSIG RR (2020-11-17 04:04:50+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-17 04:04:50+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG taaps.gov/SOA alg 8, id 64443: The value of the Signature Inception field of the RRSIG RR (2020-11-17 04:04:50+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-17 04:04:50+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG taaps.gov/TXT alg 8, id 64443: The value of the Signature Inception field of the RRSIG RR (2020-11-17 04:04:50+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-17 04:04:50+00:00). See RFC 4035, Sec. 5.3.1.
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.
taaps.gov/DS (alg 8, id 30760): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
taaps.gov/DS (alg 8, id 30760): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
taaps.gov/DS (alg 8, id 30760): 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.
taaps.gov/DS (alg 8, id 30760): 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.
qtbam3if4l.taaps.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
taaps.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
taaps.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.