View on GitHub

DNSViz: A DNS visualization tool

comcast.com

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 53929)
  • com/DS (alg 8, id 30909)
  • comcast.com/DNSKEY (alg 5, id 35356)
  • comcast.com/DNSKEY (alg 5, id 8970)
  • comcast.com/DS (alg 5, id 35356)
  • comcast.com/DS (alg 5, id 35356)

Delegation statusDelegation status

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

NoticesNotices

Warnings (18)
  • RRSIG comcast.com/A alg 5, id 8970: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.com/DNSKEY alg 5, id 35356: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.com/DNSKEY alg 5, id 35356: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.com/DNSKEY alg 5, id 8970: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.com/DNSKEY alg 5, id 8970: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.com/MX alg 5, id 8970: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.com/NS alg 5, id 8970: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.com/SOA alg 5, id 8970: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG comcast.com/TXT alg 5, id 8970: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • comcast.com/DS (alg 5, id 35356): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • comcast.com/DS (alg 5, id 35356): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • comcast.com/DS (alg 5, id 35356): 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.com/DS (alg 5, id 35356): 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.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • comcast.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • comcast.com/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • comcast.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ob4lfdcg6e.comcast.com/A 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