postar.tim.rs

Updated: 2024-06-27 20:48:38 UTC (100 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./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)

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.
postar.tim.rs/A (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (80.93.224.2, UDP_-_EDNS0_4096_D_KN)
postar.tim.rs/A (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (80.93.224.2, UDP_-_EDNS0_4096_D_KN)
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 zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.22.144.58)
tim.rs/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
postar.tim.rs/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.

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 delegation NS RRset (i.e., in the rs zone), but not in the authoritative NS RRset: ares1.tim.rs See RFC 1034, Sec. 4.2.2.
rs to tim.rs: The glue address(es) for ares1.tim.rs (185.22.144.58) differed from its authoritative address(es) (94.230.179.42). See RFC 1034, Sec. 4.2.2.