sauditelecom.com.sa

Updated: 2023-07-25 19:36:02 UTC (485 days ago) Update now

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 11019)
./DNSKEY (alg 8, id 20326)
NSEC3 proving non-existence of sauditelecom.com.sa/DS
com.sa/DNSKEY (alg 8, id 2077)
com.sa/DNSKEY (alg 8, id 23553)
com.sa/DS (alg 8, id 2077)
sa/DNSKEY (alg 8, id 26499)
sa/DNSKEY (alg 8, id 65380)
sa/DS (alg 8, id 65380)

NSEC3 proving non-existence of sauditelecom.com.sa/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 sauditelecom.com.sa/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
com.sa zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2a02:d70:64:68::2)
sa zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2a02:d70:64:68::2)
sauditelecom.com.sa/DS has errors; select the "Denial of existence" DNSSEC option to see them.

NSEC3 proving non-existence of sauditelecom.com.sa/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of sauditelecom.com.sa/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
com.sa/DNSKEY (alg 8, id 2077): 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. (2001:1490:0:800::118, UDP_-_EDNS0_4096_D_KN)
com.sa/DNSKEY (alg 8, id 23553): 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. (2001:1490:0:800::118, UDP_-_EDNS0_4096_D_KN)
sauditelecom.com.sa/DS has warnings; select the "Denial of existence" DNSSEC option to see them.