NSEC3 proving non-existence of letsencrypt.org/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 letsencrypt.org/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:502:1ca1::30, 2001:503:d414::30, 2001:503:eea3::30)
Warnings (28)
NSEC3 proving non-existence of letsencrypt.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of letsencrypt.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
RRSIG NSEC3 proving non-existence of letsencrypt.org/DS alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG NSEC3 proving non-existence of letsencrypt.org/DS alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG org/DNSKEY alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG org/DNSKEY alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG org/DNSKEY alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG org/SOA alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
akamai.net to dscq.akamai.net: The glue address(es) for n1dscq.akamai.net (23.61.195.29, 69.22.148.133) differed from its authoritative address(es) (23.61.195.29). See RFC 1034, Sec. 4.2.2.
akamai.net to dscq.akamai.net: The glue address(es) for n2dscq.akamai.net (23.61.195.38, 184.50.88.179) differed from its authoritative address(es) (23.61.195.38). See RFC 1034, Sec. 4.2.2.
akamai.net to dscq.akamai.net: The glue address(es) for n3dscq.akamai.net (23.61.195.36, 23.61.195.37) differed from its authoritative address(es) (23.61.195.37). See RFC 1034, Sec. 4.2.2.
akamai.net to dscq.akamai.net: The glue address(es) for n4dscq.akamai.net (23.61.195.30, 23.61.195.38) differed from its authoritative address(es) (23.61.195.30). See RFC 1034, Sec. 4.2.2.
akamai.net to dscq.akamai.net: The glue address(es) for n5dscq.akamai.net (63.233.60.239, 69.22.148.127) differed from its authoritative address(es) (69.22.148.127). See RFC 1034, Sec. 4.2.2.
akamai.net to dscq.akamai.net: The glue address(es) for n6dscq.akamai.net (23.61.195.29, 184.50.88.180) differed from its authoritative address(es) (184.50.88.180). See RFC 1034, Sec. 4.2.2.
akamai.net to dscq.akamai.net: The glue address(es) for n7dscq.akamai.net (23.61.195.30, 63.233.60.247) differed from its authoritative address(es) (63.233.60.247). See RFC 1034, Sec. 4.2.2.
net to akamai.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): a12-193.akamaitech.net, a5-193.akamaitech.net, zb.akamaitech.net, a6-193.akamaitech.net, a22-193.akamaitech.net, a1-193.akamaitech.net, a3-193.akamaitech.net See RFC 1034, Sec. 4.2.2.
net to akamai.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns1-1.akamaitech.net, ns6-193.akamaitech.net, ns7-193.akamaitech.net, ze.akamaitech.net, zg.akamaitech.net, zh.akamaitech.net, zi.akamaitech.net See RFC 1034, Sec. 4.2.2.
net to edgesuite.net: Authoritative AAAA records exist for a13-64.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgesuite.net: Authoritative AAAA records exist for a5-64.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgesuite.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): a11-64.akam.net, a3-64.akam.net, a9-64.akam.net See RFC 1034, Sec. 4.2.2.
net to edgesuite.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns4-65.akam.net, ns5-65.akam.net, ns7-65.akam.net See RFC 1034, Sec. 4.2.2.
org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
org/DS (alg 7, id 17883): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
org/DS (alg 7, id 17883): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.