NSEC3 proving non-existence of lxpack.pt/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 lxpack.pt/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
lxpack.pt/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (94.46.135.14, 94.46.135.27, 94.46.135.88, 94.46.135.114, UDP_-_NOEDNS_)
lxpack.pt/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (94.46.135.114, UDP_-_EDNS0_512_D_KN)
lxpack.pt/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
NSEC3 proving non-existence of lxpack.pt/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of lxpack.pt/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
mkt.lxpack.pt/CNAME: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (94.46.135.114, UDP_-_EDNS0_4096_D_KN)
mkt.lxpack.pt/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.