graybar.com
Updated:
2024-10-23 14:42:45 UTC (29 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (8)
- graybar.com/A
- graybar.com/AAAA
- graybar.com/CDNSKEY
- graybar.com/CDS
- graybar.com/MX
- graybar.com/NS
- graybar.com/SOA
- graybar.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- graybar.com/DNSKEY (alg 13, id 2371)
- graybar.com/DNSKEY (alg 13, id 34505)
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of graybar.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 29942)
- com/DS (alg 13, id 19718)
Non_existent (2)
- graybar.com/DNSKEY (alg 0, id 0)
- graybar.com/DNSKEY (alg 0, id 768)
Delegation status
Insecure (1)
- com to graybar.com
Secure (1)
- . to com
Notices
Errors (4)
- graybar.com/CDNSKEY: The CDNSKEY RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
- graybar.com/CDNSKEY: The contents of the CDNSKEY RRset are inconsistent with those of the CDS RRset. See RFC 7344, Sec. 4.
- graybar.com/CDS: The CDS RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
- graybar.com/CDS: The contents of the CDNSKEY RRset are inconsistent with those of the CDS RRset. See RFC 7344, Sec. 4.
JavaScript is required to make the graph below interactive.
