ncd.gov
Updated:
2022-08-17 17:12:33 UTC (610 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Bogus (2)
- ncd.gov/SOA
- ncd.gov/TXT
Secure (3)
- ncd.gov/A
- ncd.gov/MX
- ncd.gov/NS
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- gov/DNSKEY (alg 8, id 261)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ncd.gov/DNSKEY (alg 5, id 33278)
- ncd.gov/DNSKEY (alg 5, id 8907)
- ncd.gov/DS (alg 5, id 33278)
- ncd.gov/DS (alg 5, id 33278)
Delegation status
Secure (2)
- . to gov
- gov to ncd.gov
Notices
Errors (2)
- RRSIG ncd.gov/SOA alg 5, id 8907: The cryptographic signature of the RRSIG RR does not properly validate.
- RRSIG ncd.gov/TXT alg 5, id 8907: The cryptographic signature of the RRSIG RR does not properly validate.
Warnings (19)
- RRSIG ncd.gov/A alg 5, id 8907: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG ncd.gov/DNSKEY alg 5, id 33278: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG ncd.gov/DNSKEY alg 5, id 33278: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG ncd.gov/MX alg 5, id 8907: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG ncd.gov/NS alg 5, id 8907: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG ncd.gov/SOA alg 5, id 8907: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG ncd.gov/TXT alg 5, id 8907: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- gov to ncd.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns3.milesdns.com
- ncd.gov/A: The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. (13.82.63.61, UDP_-_EDNS0_4096_D_KN)
- ncd.gov/DNSKEY (alg 5, id 33278): The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. (13.82.63.61, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- ncd.gov/DNSKEY (alg 5, id 8907): The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. (13.82.63.61, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- ncd.gov/DS (alg 5, id 33278): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- ncd.gov/DS (alg 5, id 33278): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- ncd.gov/DS (alg 5, id 33278): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
- ncd.gov/DS (alg 5, id 33278): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
- ncd.gov/MX: The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. (13.82.63.61, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- ncd.gov/NS: The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. (13.82.63.61, UDP_-_EDNS0_4096_D_KN)
- ncd.gov/SOA: The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. (13.82.63.61, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- ncd.gov/TXT: The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. (13.82.63.61, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
