View on GitHub

DNSViz: A DNS visualization tool

byte.ma

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

RRset statusRRset status

Bogus (2)
  • byte.ma/NS
  • byte.ma/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • byte.ma/DNSKEY (alg 13, id 2371)
  • byte.ma/DNSKEY (alg 13, id 34505)
Secure (9)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • byte.ma/DS (alg 5, id 257)
  • ma/DNSKEY (alg 8, id 26121)
  • ma/DNSKEY (alg 8, id 33982)
  • ma/DNSKEY (alg 8, id 3798)
  • ma/DNSKEY (alg 8, id 46261)
  • ma/DS (alg 8, id 46261)
Non_existent (1)
  • byte.ma/DNSKEY (alg 5, id 257)

Delegation statusDelegation status

Bogus (1)
  • ma to byte.ma
Secure (1)
  • . to ma

NoticesNotices

Errors (13)
  • byte.ma/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.73, 108.162.193.238, 172.64.32.73, 172.64.33.238, 173.245.58.73, 173.245.59.238, 2606:4700:50::adf5:3a49, 2606:4700:58::adf5:3bee, 2803:f800:50::6ca2:c049, 2803:f800:50::6ca2:c1ee, 2a06:98c1:50::ac40:2049, 2a06:98c1:50::ac40:21ee, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • byte.ma/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.73, 108.162.193.238, 172.64.32.73, 172.64.33.238, 173.245.58.73, 173.245.59.238, 2606:4700:50::adf5:3a49, 2606:4700:58::adf5:3bee, 2803:f800:50::6ca2:c049, 2803:f800:50::6ca2:c1ee, 2a06:98c1:50::ac40:2049, 2a06:98c1:50::ac40:21ee, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • byte.ma/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.73, 108.162.193.238, 172.64.32.73, 172.64.33.238, 173.245.58.73, 173.245.59.238, 2606:4700:50::adf5:3a49, 2606:4700:58::adf5:3bee, 2803:f800:50::6ca2:c049, 2803:f800:50::6ca2:c1ee, 2a06:98c1:50::ac40:2049, 2a06:98c1:50::ac40:21ee, UDP_-_EDNS0_4096_D_KN)
  • byte.ma/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.73, 108.162.193.238, 172.64.32.73, 172.64.33.238, 173.245.58.73, 173.245.59.238, 2606:4700:50::adf5:3a49, 2606:4700:58::adf5:3bee, 2803:f800:50::6ca2:c049, 2803:f800:50::6ca2:c1ee, 2a06:98c1:50::ac40:2049, 2a06:98c1:50::ac40:21ee, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ma to byte.ma: 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.73, 108.162.193.238, 172.64.32.73, 172.64.33.238, 173.245.58.73, 173.245.59.238, 2606:4700:50::adf5:3a49, 2606:4700:58::adf5:3bee, 2803:f800:50::6ca2:c049, 2803:f800:50::6ca2:c1ee, 2a06:98c1:50::ac40:2049, 2a06:98c1:50::ac40:21ee, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ma to byte.ma: 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.73, 108.162.193.238, 172.64.32.73, 172.64.33.238, 173.245.58.73, 173.245.59.238, 2606:4700:50::adf5:3a49, 2606:4700:58::adf5:3bee, 2803:f800:50::6ca2:c049, 2803:f800:50::6ca2:c1ee, 2a06:98c1:50::ac40:2049, 2a06:98c1:50::ac40:21ee, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • byte.ma/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • byte.ma/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • jyxfv7dt5r.byte.ma/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • byte.ma/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • byte.ma/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • byte.ma/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • byte.ma/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • ma/DNSKEY (alg 8, id 26121): 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. (41.214.240.4, UDP_-_EDNS0_4096_D_KN)
  • ma/DNSKEY (alg 8, id 33982): 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. (41.214.240.4, UDP_-_EDNS0_4096_D_KN)
  • ma/DNSKEY (alg 8, id 3798): 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. (41.214.240.4, UDP_-_EDNS0_4096_D_KN)
  • ma/DNSKEY (alg 8, id 46261): 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. (41.214.240.4, UDP_-_EDNS0_4096_D_KN)

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