ptt.gov
Updated:
2022-05-30 17:58:12 UTC (907 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- ptt.gov/NS
- ptt.gov/NSEC3PARAM
- ptt.gov/SOA
- ptt.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- gov/DNSKEY (alg 8, id 2706)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ptt.gov/DNSKEY (alg 8, id 34945)
- ptt.gov/DNSKEY (alg 8, id 4121)
- ptt.gov/DS (alg 8, id 4121)
- ptt.gov/DS (alg 8, id 4121)
Delegation status
Secure (2)
- . to gov
- gov to ptt.gov
Notices
Errors (5)
- ptt.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- ptt.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- ptt.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- ptt.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- 7eh24brock.ptt.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- ptt.gov/DS (alg 8, id 4121): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ptt.gov/DS (alg 8, id 4121): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ptt.gov/DS (alg 8, id 4121): 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.
- ptt.gov/DS (alg 8, id 4121): 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.
JavaScript is required to make the graph below interactive.
