postar.tim.rs
Updated:
2024-06-28 13:50:04 UTC (8 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (1)
- postar.tim.rs/A
Secure (1)
- rs/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 5613)
- NSEC3 proving non-existence of tim.rs/DS
- rs/DNSKEY (alg 13, id 23736)
- rs/DNSKEY (alg 13, id 29729)
- rs/DNSKEY (alg 13, id 57382)
- rs/DS (alg 13, id 57382)
Delegation status
Insecure (1)
- rs to tim.rs
Secure (1)
- . to rs
Notices
Errors (4)
- NSEC3 proving non-existence of tim.rs/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of tim.rs/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- tim.rs zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (80.93.224.2)
- tim.rs/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of tim.rs/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of tim.rs/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- rs to tim.rs: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the rs zone): ns2.absolutok.com See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
