pbgc.gov
Updated:
2021-02-12 18:17:05 UTC (1378 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- pbgc.gov/A
- pbgc.gov/MX
- pbgc.gov/NS
- pbgc.gov/SOA
- pbgc.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./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)
- gov/DS (alg 8, id 7698)
- pbgc.gov/DNSKEY (alg 5, id 17221)
- pbgc.gov/DNSKEY (alg 5, id 60303)
- pbgc.gov/DS (alg 5, id 17221)
- pbgc.gov/DS (alg 5, id 17221)
Delegation status
Secure (2)
- . to gov
- gov to pbgc.gov
Notices
Warnings (21)
- RRSIG pbgc.gov/A alg 5, id 60303: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG pbgc.gov/DNSKEY alg 5, id 17221: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG pbgc.gov/DNSKEY alg 5, id 17221: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG pbgc.gov/DNSKEY alg 5, id 60303: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG pbgc.gov/DNSKEY alg 5, id 60303: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG pbgc.gov/MX alg 5, id 60303: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG pbgc.gov/NS alg 5, id 60303: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG pbgc.gov/SOA alg 5, id 60303: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG pbgc.gov/TXT alg 5, id 60303: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 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.
- pbgc.gov/DS (alg 5, id 17221): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pbgc.gov/DS (alg 5, id 17221): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pbgc.gov/DS (alg 5, id 17221): 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.
- pbgc.gov/DS (alg 5, id 17221): 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.
- 8z7wmdroc0.pbgc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- pbgc.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- pbgc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- pbgc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
