RRSIG eia.gov/A alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/A alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/AAAA alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/AAAA alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/DNSKEY alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/DNSKEY alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/DNSKEY alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/DNSKEY alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/DNSKEY alg 5, id 35626: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/DNSKEY alg 5, id 35626: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/DNSKEY alg 5, id 48502: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/DNSKEY alg 5, id 48502: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/MX alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/MX alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/NS alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/NS alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/SOA alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/SOA alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/TXT alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eia.gov/TXT alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
eia.gov/DNSKEY (alg 5, id 35626): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (205.254.135.9, 2607:f368:1000:1001::1009, TCP_-_EDNS0_4096_D_K)
eia.gov/DNSKEY (alg 5, id 48502): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (205.254.159.231, UDP_-_EDNS0_4096_D_K)
eia.gov/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (205.254.135.9, 205.254.159.231, 2607:f368:1000:1001::1009, UDP_-_EDNS0_512_D_K)
eia.gov/DNSKEY: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (205.254.135.9, 205.254.159.231, 2607:f368:1000:1001::1009, UDP_-_EDNS0_512_D_K)
eia.gov/DS (alg 5, id 34806): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
eia.gov/DS (alg 5, id 34806): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov to eia.gov: Authoritative AAAA records exist for phantom.eia.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.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): 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.
eia.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
8wt1phf2ui.eia.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
eia.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.