View on GitHub

DNSViz: A DNS visualization tool

af.mil

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (3)
  • af.mil/NS
  • af.mil/SOA
  • af.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • af.mil/DNSKEY (alg 8, id 44976)
  • af.mil/DNSKEY (alg 8, id 47250)
  • af.mil/DNSKEY (alg 8, id 56521)
  • af.mil/DNSKEY (alg 8, id 9826)
  • af.mil/DS (alg 8, id 56521)
  • af.mil/DS (alg 8, id 56521)
  • mil/DNSKEY (alg 8, id 15684)
  • mil/DNSKEY (alg 8, id 4983)
  • mil/DNSKEY (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)

Delegation statusDelegation status

Secure (2)
  • . to mil
  • mil to af.mil

NoticesNotices

Errors (23)
  • RRSIG af.mil/DNSKEY alg 8, id 47250: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 47250: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 47250: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 47250: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 56521: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 56521: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 56521: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 56521: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 9826: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 9826: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 9826: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG af.mil/DNSKEY alg 8, id 9826: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • af.mil/DS (alg 8, id 56521): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • af.mil/DS (alg 8, id 56521): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil to af.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (132.3.13.10, 132.3.29.10, UDP_-_EDNS0_4096_D_K)
  • mil/DS (alg 8, id 7765): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 7765): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • af.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • af.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • 87b1j5s92h.af.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • af.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • af.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • af.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • af.mil/DS (alg 8, id 56521): 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 56521): 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/SOA: 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. (132.3.57.10, UDP_-_EDNS0_4096_D_K)
  • mil/DS (alg 8, id 7765): 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.
  • mil/DS (alg 8, id 7765): 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.
  • 87b1j5s92h.af.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • af.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • af.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • af.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • af.mil/MX 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