co.ug

Updated: 2020-06-14 11:35:41 UTC (1665 days ago) Update now

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

NSEC3 proving non-existence of co.ug/A: 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 co.ug/A: 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 co.ug/AAAA: 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 co.ug/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
ug/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.

. to ug: AAAA glue records exist for anycast.eahd.or.ug, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
. to ug: The following NS name(s) were found in the delegation NS RRset (i.e., in the . zone), but not in the authoritative NS RRset: ug.cctld.authdns.ripe.net See RFC 1034, Sec. 4.2.2.
NSEC3 proving non-existence of co.ug/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of co.ug/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of co.ug/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of co.ug/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
ug/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.