teknokrat.ac.id
Updated:
2024-10-23 05:13:02 UTC (31 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (8)
- teknokrat.ac.id/A
- teknokrat.ac.id/AAAA
- teknokrat.ac.id/CDNSKEY
- teknokrat.ac.id/CDS
- teknokrat.ac.id/MX
- teknokrat.ac.id/NS
- teknokrat.ac.id/SOA
- teknokrat.ac.id/TXT
Secure (2)
- ac.id/SOA
- ac.id/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- teknokrat.ac.id/DNSKEY (alg 13, id 2371)
- teknokrat.ac.id/DNSKEY (alg 13, id 34505)
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC proving non-existence of teknokrat.ac.id/DS
- ac.id/DNSKEY (alg 8, id 30876)
- ac.id/DNSKEY (alg 8, id 46909)
- ac.id/DS (alg 8, id 46909)
- id/DNSKEY (alg 8, id 22449)
- id/DNSKEY (alg 8, id 26887)
- id/DS (alg 8, id 26887)
Delegation status
Insecure (1)
- ac.id to teknokrat.ac.id
Secure (2)
- . to id
- id to ac.id
Notices
Errors (4)
- ac.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:c::c, 2402:ee80:d::d)
- id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:c::c, 2402:ee80:d::d)
- teknokrat.ac.id/CDNSKEY: The CDNSKEY RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
- teknokrat.ac.id/CDS: The CDS RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
JavaScript is required to make the graph below interactive.
