comcast.com
Updated:
2022-01-14 17:30:18 UTC (1073 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- comcast.com/A
- comcast.com/MX
- comcast.com/NS
- comcast.com/SOA
- comcast.com/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- com/DNSKEY (alg 8, id 15549)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 38535)
- 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 status
Secure (2)
- . to com
- com to comcast.com
Notices
Warnings (20)
- 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.
- com/DS (alg 8, id 30909): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.5.5.241, UDP_-_EDNS0_4096_D_KN)
- com/DS (alg 8, id 30909): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.5.5.241, UDP_-_EDNS0_4096_D_KN)
- 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.
- w56fjph3zy.comcast.com/A 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.
JavaScript is required to make the graph below interactive.
