View on GitHub

DNSViz: A DNS visualization tool

mydhl.express.dhl

Updated: 2023-11-24 07:11:47 UTC (about a year ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (4)
  • akamaiedge.net/SOA
  • e9324.a.akamaiedge.net/A
  • mydhl.express.dhl.new.edgekey.net/CNAME
  • mydhl.express.dhl/CNAME
Secure (5)
  • dhl/SOA
  • dhl/SOA
  • net/SOA
  • net/SOA
  • net/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC3 proving non-existence of akamaiedge.net/DS
  • NSEC3 proving non-existence of edgekey.net/DS
  • NSEC3 proving non-existence of express.dhl/DS
  • dhl/DNSKEY (alg 13, id 28795)
  • dhl/DNSKEY (alg 13, id 49092)
  • dhl/DS (alg 13, id 2817)
  • dhl/DS (alg 13, id 28795)
  • dhl/DS (alg 7, id 31860)
  • net/DNSKEY (alg 13, id 37331)
  • net/DNSKEY (alg 13, id 44222)
  • net/DS (alg 13, id 37331)
Non_existent (2)
  • dhl/DNSKEY (alg 13, id 2817)
  • dhl/DNSKEY (alg 7, id 31860)

Delegation statusDelegation status

Insecure (4)
  • akamaiedge.net to a.akamaiedge.net
  • dhl to express.dhl
  • net to akamaiedge.net
  • net to edgekey.net
Secure (2)
  • . to dhl
  • . to net

NoticesNotices

Errors (8)
  • . to dhl: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.24.64.82, 194.169.218.82, 212.18.248.82, 212.18.249.82, 2001:67c:13cc::1:82, 2a04:2b00:13cc::1:82, 2a04:2b00:13ee::82, 2a04:2b00:13ff::82, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • NSEC3 proving non-existence of express.dhl/DS: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.24.64.82, 194.169.218.82, 212.18.248.82, 212.18.249.82, 2001:67c:13cc::1:82, 2a04:2b00:13cc::1:82, 2a04:2b00:13ee::82, 2a04:2b00:13ff::82, UDP_-_EDNS0_4096_D_KN)
  • akamaiedge.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2600:1406:32::c2)
  • dhl/DNSKEY (alg 13, id 28795): The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.24.64.82, 194.169.218.82, 212.18.248.82, 212.18.249.82, 2001:67c:13cc::1:82, 2a04:2b00:13cc::1:82, 2a04:2b00:13ee::82, 2a04:2b00:13ff::82, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • dhl/DNSKEY (alg 13, id 49092): The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.24.64.82, 194.169.218.82, 212.18.248.82, 212.18.249.82, 2001:67c:13cc::1:82, 2a04:2b00:13cc::1:82, 2a04:2b00:13ee::82, 2a04:2b00:13ff::82, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • dhl/SOA: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.24.64.82, 212.18.249.82, 2a04:2b00:13cc::1:82, 2a04:2b00:13ff::82, UDP_-_EDNS0_4096_D_KN)
  • dhl/SOA: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (194.169.218.82, 212.18.248.82, 2001:67c:13cc::1:82, 2a04:2b00:13ee::82, UDP_-_EDNS0_4096_D_KN)
  • edgekey.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2600:1406:32::40)
Warnings (13)
  • akamaiedge.net to a.akamaiedge.net: The glue address(es) for n1a.akamaiedge.net (184.51.100.5, 184.51.100.12) differed from its authoritative address(es) (184.51.100.5). See RFC 1034, Sec. 4.2.2.
  • akamaiedge.net to a.akamaiedge.net: The glue address(es) for n1a.akamaiedge.net (2600:1406:1a:f000:6405::, 2600:1406:1a:f000:6405:dc72:9ccd:dcf8, 2600:1406:1a:f000:640c:dc72:9ccd:dcf8) differed from its authoritative address(es) (2600:1406:1a:f000:640c:dc72:9ccd:dcf8). See RFC 1034, Sec. 4.2.2.
  • akamaiedge.net to a.akamaiedge.net: The glue address(es) for n2a.akamaiedge.net (23.200.73.220, 23.200.73.223) differed from its authoritative address(es) (23.200.73.220). See RFC 1034, Sec. 4.2.2.
  • akamaiedge.net to a.akamaiedge.net: The glue address(es) for n3a.akamaiedge.net (23.200.73.218, 23.200.73.220) differed from its authoritative address(es) (23.200.73.218). See RFC 1034, Sec. 4.2.2.
  • akamaiedge.net to a.akamaiedge.net: The glue address(es) for n5a.akamaiedge.net (23.200.73.216, 23.200.73.222) differed from its authoritative address(es) (23.200.73.216). See RFC 1034, Sec. 4.2.2.
  • akamaiedge.net to a.akamaiedge.net: The glue address(es) for n6a.akamaiedge.net (23.200.73.216, 23.200.73.222) differed from its authoritative address(es) (23.200.73.222). See RFC 1034, Sec. 4.2.2.
  • dhl to express.dhl: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the dhl zone): ns2b.dhl.com, ns2.dhl.com See RFC 1034, Sec. 4.2.2.
  • dhl to express.dhl: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (212.18.248.82, 2a04:2b00:13ee::82, UDP_-_EDNS0_4096_D_KN)
  • dhl/DNSKEY (alg 13, id 28795): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (212.18.248.82, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • dhl/DNSKEY (alg 13, id 49092): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (212.18.248.82, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • net to akamaiedge.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): ns5-194.akamaiedge.net, a11-192.akamaiedge.net, a13-192.akamaiedge.net, ns6-194.akamaiedge.net, ns7-194.akamaiedge.net See RFC 1034, Sec. 4.2.2.
  • net to edgekey.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): adns1.akam.net, a11-65.akam.net, a13-65.akam.net, a3-65.akam.net, ns1-2.akam.net, a9-65.akam.net, usw6.akam.net, a5-65.akam.net See RFC 1034, Sec. 4.2.2.
  • net to edgekey.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: a1-66.akam.net, a10-66.akam.net, a7-64.akam.net See RFC 1034, Sec. 4.2.2.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph