View on GitHub

DNSViz: A DNS visualization tool

comcast.net

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

RRset statusRRset status

Secure (5)
  • comcast.net/A
  • comcast.net/MX
  • comcast.net/NS
  • comcast.net/SOA
  • comcast.net/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • ./DNSKEY (alg 8, id 951)
  • comcast.net/DNSKEY (alg 5, id 26550)
  • comcast.net/DNSKEY (alg 5, id 40909)
  • comcast.net/DS (alg 5, id 40909)
  • comcast.net/DS (alg 5, id 40909)
  • net/DNSKEY (alg 8, id 27254)
  • net/DNSKEY (alg 8, id 35886)
  • net/DS (alg 8, id 35886)

Delegation statusDelegation status

Secure (2)
  • . to net
  • net to comcast.net

NoticesNotices

Errors (8)
  • comcast.net zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (68.87.68.244, 68.87.72.244, 68.87.76.228, 68.87.85.132, 69.252.250.103, 2001:558:1004:7:68:87:85:132, 2001:558:100a:5:68:87:68:244, 2001:558:1014:c:68:87:76:228)
  • comcast.net/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (68.87.68.244, UDP_-_EDNS0_512_D_KN)
  • comcast.net/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (68.87.68.244, UDP_-_NOEDNS_)
  • comcast.net/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (68.87.68.244, 69.252.250.103, UDP_-_EDNS0_512_D_KN)
  • comcast.net/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (68.87.68.244, 68.87.72.244, 68.87.76.228, 68.87.85.132, 69.252.250.103, 2001:558:1004:7:68:87:85:132, 2001:558:100a:5:68:87:68:244, 2001:558:1014:c:68:87:76:228, TCP_-_EDNS0_4096_D_N)
  • comcast.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • comcast.net/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • comcast.net/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (20)
  • RRSIG comcast.net/A alg 5, id 26550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.net/DNSKEY alg 5, id 26550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.net/DNSKEY alg 5, id 26550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.net/DNSKEY alg 5, id 40909: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.net/DNSKEY alg 5, id 40909: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.net/MX alg 5, id 26550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.net/NS alg 5, id 26550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.net/SOA alg 5, id 26550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.net/TXT alg 5, id 26550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • comcast.net/DS (alg 5, id 40909): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • comcast.net/DS (alg 5, id 40909): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • comcast.net/DS (alg 5, id 40909): 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.
  • comcast.net/DS (alg 5, id 40909): 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.
  • comcast.net/NS: 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. (68.87.76.228, UDP_-_EDNS0_4096_D_KN)
  • comcast.net/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (69.252.250.103, UDP_-_EDNS0_4096_D_KN)
  • comcast.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • comcast.net/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • comcast.net/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 2839cbf6qx.comcast.net/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • comcast.net/AAAA 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