ptt.gov
Updated:
2024-01-18 00:11:26 UTC (136 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (4)
- ptt.gov/NS
- ptt.gov/NSEC3PARAM
- ptt.gov/SOA
- ptt.gov/TXT
DNSKEY/DS/NSEC status
Bogus (3)
- ptt.gov/DNSKEY (alg 8, id 27131)
- ptt.gov/DNSKEY (alg 8, id 45317)
- ptt.gov/DNSKEY (alg 8, id 58258)
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- gov/DNSKEY (alg 8, id 10104)
- gov/DNSKEY (alg 8, id 49735)
- gov/DNSKEY (alg 8, id 64280)
- gov/DS (alg 8, id 64280)
- ptt.gov/DS (alg 8, id 35989)
- ptt.gov/DS (alg 8, id 45317)
Non_existent (1)
- ptt.gov/DNSKEY (alg 8, id 35989)
Delegation status
Bogus (1)
- gov to ptt.gov
Secure (1)
- . to gov
Notices
Errors (7)
- gov to ptt.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. (13.248.142.184, 13.248.144.182, 13.248.149.147, 76.223.9.162, 76.223.24.135, 2600:1f14:653:bb00:b24e:739c:b87d:8fee, 2600:1f16:8f2:d500::4, UDP_-_EDNS0_4096_D_KN)
- gov to ptt.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. (13.248.142.184, 13.248.144.182, 13.248.149.147, 76.223.9.162, 76.223.24.135, 2600:1f14:653:bb00:b24e:739c:b87d:8fee, 2600:1f16:8f2:d500::4, UDP_-_EDNS0_4096_D_KN)
- 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.
- bru9qa8tch.ptt.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
