feedthefuture.gov

Updated: 2020-10-11 19:25:59 UTC (1504 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Bogus (4)

feedthefuture.gov/A
feedthefuture.gov/NS
feedthefuture.gov/SOA
feedthefuture.gov/TXT

DNSKEY/DS/NSEC status

Bogus (2)

feedthefuture.gov/DNSKEY (alg 8, id 14554)
feedthefuture.gov/DNSKEY (alg 8, id 54240)

Secure (11)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 26116)
feedthefuture.gov/DS (alg 8, id 14554)
feedthefuture.gov/DS (alg 8, id 14554)
feedthefuture.gov/DS (alg 8, id 2440)
feedthefuture.gov/DS (alg 8, id 32530)
gov/DNSKEY (alg 8, id 15489)
gov/DNSKEY (alg 8, id 26665)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)
gov/DS (alg 8, id 7698)

Non_existent (2)

feedthefuture.gov/DNSKEY (alg 8, id 2440)
feedthefuture.gov/DNSKEY (alg 8, id 32530)

Delegation status

Bogus (1)

gov to feedthefuture.gov

Secure (1)

. to gov

Notices

Errors (13)

feedthefuture.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (12.96.42.221, 152.180.39.93, UDP_-_EDNS0_4096_D_K)
feedthefuture.gov/DNSKEY (alg 8, id 14554): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (12.96.42.221, 152.180.39.93, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
feedthefuture.gov/DNSKEY (alg 8, id 54240): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (12.96.42.221, 152.180.39.93, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
feedthefuture.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (12.96.42.221, 152.180.39.93, UDP_-_EDNS0_4096_D_K)
feedthefuture.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (12.96.42.221, 152.180.39.93, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
feedthefuture.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (12.96.42.221, 152.180.39.93, UDP_-_EDNS0_4096_D_K)
gov to feedthefuture.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. (12.96.42.221, 152.180.39.93, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
gov to feedthefuture.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. (12.96.42.221, 152.180.39.93, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
feedthefuture.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
feedthefuture.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
feedthefuture.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
e1oag3rnix.feedthefuture.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
feedthefuture.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (12)

feedthefuture.gov/DS (alg 8, id 14554): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
feedthefuture.gov/DS (alg 8, id 14554): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
feedthefuture.gov/DS (alg 8, id 14554): 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.
feedthefuture.gov/DS (alg 8, id 14554): 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.
feedthefuture.gov/DS (alg 8, id 2440): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
feedthefuture.gov/DS (alg 8, id 2440): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
feedthefuture.gov/DS (alg 8, id 2440): 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.
feedthefuture.gov/DS (alg 8, id 2440): 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): 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.