View on GitHub

DNSViz: A DNS visualization tool

nickersonm.com

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

RRset statusRRset status

Bogus (5)
  • nickersonm.com/A
  • nickersonm.com/MX
  • nickersonm.com/NS
  • nickersonm.com/SOA
  • nickersonm.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • nickersonm.com/DNSKEY (alg 13, id 2371)
  • nickersonm.com/DNSKEY (alg 13, id 34505)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 38535)
  • com/DS (alg 8, id 30909)
  • nickersonm.com/DS (alg 5, id 34756)
Non_existent (1)
  • nickersonm.com/DNSKEY (alg 5, id 34756)

Delegation statusDelegation status

Bogus (1)
  • com to nickersonm.com
Secure (1)
  • . to com

NoticesNotices

Errors (14)
  • com to nickersonm.com: 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. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • com to nickersonm.com: The DS RRset for the zone included algorithm 5 (RSASHA1), but no DS RR matched a DNSKEY with algorithm 5 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • nickersonm.com/A: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN)
  • nickersonm.com/DNSKEY (alg 13, id 2371): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • nickersonm.com/DNSKEY (alg 13, id 34505): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • nickersonm.com/MX: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • nickersonm.com/NS: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN)
  • nickersonm.com/SOA: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • nickersonm.com/TXT: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN)
  • nickersonm.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • nickersonm.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • nickersonm.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • b2q0r7agzt.nickersonm.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nickersonm.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
  • ./DNSKEY (alg 8, id 20326): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 9799): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • nickersonm.com/DS (alg 5, id 34756): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nickersonm.com/DS (alg 5, id 34756): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nickersonm.com/DS (alg 5, id 34756): 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.
  • nickersonm.com/DS (alg 5, id 34756): 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.

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