NSEC3 proving non-existence of uol.com.br/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 uol.com.br/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 uol.com.br/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 uol.com.br/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 uol.com.br/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 uol.com.br/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
br zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:12f8:c::10)
com.br zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:12f8:c::10)
Warnings (8)
NSEC3 proving non-existence of uol.com.br/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of uol.com.br/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of uol.com.br/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of uol.com.br/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of uol.com.br/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of uol.com.br/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
cloudfront.net to dftex7xfha8fh.cloudfront.net: The server(s) for the parent zone (cloudfront.net) responded with a referral instead of answering authoritatively for the DS RR type. See RFC 4034, Sec. 5. (205.251.193.162, 205.251.194.154, 205.251.197.26, 205.251.198.61, 2600:9000:5301:a200::1, 2600:9000:5302:9a00::1, 2600:9000:5305:1a00::1, 2600:9000:5306:3d00::1, UDP_-_EDNS0_4096_D_K)
net to cloudfront.net: Authoritative AAAA records exist for ns-666.awsdns-19.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.