pepfar.gov
Updated:
2022-01-27 13:50:48 UTC (1028 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- pepfar.gov/A
- pepfar.gov/AAAA
- pepfar.gov/NS
- pepfar.gov/NSEC3PARAM
- pepfar.gov/SOA
- pepfar.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- pepfar.gov/DNSKEY (alg 8, id 23836)
- pepfar.gov/DNSKEY (alg 8, id 55398)
- pepfar.gov/DNSKEY (alg 8, id 65238)
- pepfar.gov/DS (alg 8, id 23836)
- pepfar.gov/DS (alg 8, id 23836)
Delegation status
Secure (2)
- . to gov
- gov to pepfar.gov
Notices
Errors (3)
- pepfar.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- pepfar.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- ck29w4u0qz.pepfar.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- pepfar.gov/DS (alg 8, id 23836): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pepfar.gov/DS (alg 8, id 23836): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pepfar.gov/DS (alg 8, id 23836): 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.
- pepfar.gov/DS (alg 8, id 23836): 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.
- pepfar.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- pepfar.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- ck29w4u0qz.pepfar.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
