occ.gov
Updated:
2021-01-13 11:21:38 UTC (1411 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- occ.gov/A
- occ.gov/AAAA
- occ.gov/NS
- occ.gov/SOA
- occ.gov/SOA
- occ.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- gov/DNSKEY (alg 8, id 15489)
- gov/DNSKEY (alg 8, id 27306)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- occ.gov/DNSKEY (alg 8, id 1980)
- occ.gov/DNSKEY (alg 8, id 30426)
- occ.gov/DNSKEY (alg 8, id 50800)
- occ.gov/DS (alg 8, id 50800)
- occ.gov/DS (alg 8, id 50800)
Delegation status
Secure (2)
- . to gov
- gov to occ.gov
Notices
Errors (5)
- occ.gov/DNSKEY (alg 8, id 1980): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
- occ.gov/DNSKEY (alg 8, id 30426): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (164.95.95.155, 2610:108:3000:100a::155, UDP_-_EDNS0_4096_D_KN)
- kqy26we0jd.occ.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- occ.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- occ.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): 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.
- gov/DS (alg 8, id 7698): 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.
- gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
- gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
- gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
- gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
- occ.gov/DS (alg 8, id 50800): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- occ.gov/DS (alg 8, id 50800): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- occ.gov/DS (alg 8, id 50800): 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.
- occ.gov/DS (alg 8, id 50800): 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.
- kqy26we0jd.occ.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- occ.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- occ.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
