superior.boulder.noaa.gov

Updated: 2021-02-21 05:31:43 UTC (1759 days ago) Update now

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

Secure (1)

superior.boulder.noaa.gov/A

DNSKEY/DS/NSEC status

Secure (16)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 42351)
boulder.noaa.gov/DNSKEY (alg 5, id 31954)
boulder.noaa.gov/DNSKEY (alg 5, id 38010)
boulder.noaa.gov/DNSKEY (alg 5, id 53922)
boulder.noaa.gov/DS (alg 5, id 31954)
boulder.noaa.gov/DS (alg 5, id 31954)
gov/DNSKEY (alg 8, id 27306)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)
gov/DS (alg 8, id 7698)
noaa.gov/DNSKEY (alg 5, id 38733)
noaa.gov/DNSKEY (alg 5, id 46807)
noaa.gov/DNSKEY (alg 5, id 46995)
noaa.gov/DS (alg 5, id 46807)
noaa.gov/DS (alg 5, id 46807)

Delegation status

Secure (3)

. to gov
gov to noaa.gov
noaa.gov to boulder.noaa.gov

Notices

Warnings (29)

RRSIG boulder.noaa.gov/DNSKEY alg 5, id 31954: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG boulder.noaa.gov/DNSKEY alg 5, id 31954: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG boulder.noaa.gov/DNSKEY alg 5, id 31954: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG boulder.noaa.gov/DNSKEY alg 5, id 53922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG boulder.noaa.gov/DNSKEY alg 5, id 53922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG boulder.noaa.gov/DNSKEY alg 5, id 53922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG boulder.noaa.gov/DS alg 5, id 38733: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG boulder.noaa.gov/DS alg 5, id 38733: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG noaa.gov/DNSKEY alg 5, id 38733: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG noaa.gov/DNSKEY alg 5, id 38733: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG noaa.gov/DNSKEY alg 5, id 38733: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG noaa.gov/DNSKEY alg 5, id 46807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG noaa.gov/DNSKEY alg 5, id 46807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG noaa.gov/DNSKEY alg 5, id 46807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG superior.boulder.noaa.gov/A alg 5, id 53922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
boulder.noaa.gov/DS (alg 5, id 31954): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
boulder.noaa.gov/DS (alg 5, id 31954): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
boulder.noaa.gov/DS (alg 5, id 31954): 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.
boulder.noaa.gov/DS (alg 5, id 31954): 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.
noaa.gov/DS (alg 5, id 46807): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
noaa.gov/DS (alg 5, id 46807): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
noaa.gov/DS (alg 5, id 46807): 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.
noaa.gov/DS (alg 5, id 46807): 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.
boulder.noaa.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
superior.boulder.noaa.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.