View on GitHub

DNSViz: A DNS visualization tool

www.af.mil

Updated: 2024-06-10 13:29:49 UTC (277 days 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
  • e11218.dscb.akamaiedge.net/A
  • e11218.dscb.akamaiedge.net/AAAA
  • www.afpw.af.mil.edgekey.net/CNAME
Secure (4)
  • net/SOA
  • net/SOA
  • net/SOA
  • www.af.mil/CNAME

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (17)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • NSEC3 proving non-existence of akamaiedge.net/DS
  • NSEC3 proving non-existence of edgekey.net/DS
  • af.mil/DNSKEY (alg 8, id 15258)
  • af.mil/DNSKEY (alg 8, id 15529)
  • af.mil/DNSKEY (alg 8, id 2725)
  • af.mil/DNSKEY (alg 8, id 495)
  • af.mil/DS (alg 8, id 15529)
  • af.mil/DS (alg 8, id 15529)
  • mil/DNSKEY (alg 8, id 16801)
  • mil/DNSKEY (alg 8, id 45154)
  • mil/DNSKEY (alg 8, id 9246)
  • mil/DS (alg 8, id 16801)
  • net/DNSKEY (alg 13, id 37331)
  • net/DNSKEY (alg 13, id 51809)
  • net/DS (alg 13, id 37331)

Delegation statusDelegation status

Insecure (3)
  • akamaiedge.net to dscb.akamaiedge.net
  • net to akamaiedge.net
  • net to edgekey.net
Secure (3)
  • . to mil
  • . to net
  • mil to af.mil

NoticesNotices

Errors (1)
  • af.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • af.mil/DS (alg 8, id 15529): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • af.mil/DS (alg 8, id 15529): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • af.mil/DS (alg 8, id 15529): 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.
  • af.mil/DS (alg 8, id 15529): 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.
  • 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.
  • af.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.

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