ntsb.gov
Updated:
2020-06-27 06:53:38 UTC (1616 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- ntsb.gov/A
- ntsb.gov/MX
- ntsb.gov/NS
- ntsb.gov/SOA
- ntsb.gov/TXT
DNSKEY/DS/NSEC status
Secure (15)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- ./DNSKEY (alg 8, id 48903)
- gov/DNSKEY (alg 8, id 40176)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ntsb.gov/DNSKEY (alg 8, id 14297)
- ntsb.gov/DNSKEY (alg 8, id 303)
- ntsb.gov/DNSKEY (alg 8, id 60363)
- ntsb.gov/DNSKEY (alg 8, id 62572)
- ntsb.gov/DS (alg 8, id 14297)
- ntsb.gov/DS (alg 8, id 14297)
- ntsb.gov/DS (alg 8, id 62572)
- ntsb.gov/DS (alg 8, id 62572)
Delegation status
Secure (2)
- . to gov
- gov to ntsb.gov
Notices
Errors (5)
- ntsb.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.173.155.4, 199.173.155.5)
- ntsb.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (199.173.155.4, 199.173.155.5, TCP_-_EDNS0_4096_D)
- 8cbkfuh4iz.ntsb.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ntsb.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- ntsb.gov/CNAME 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.
- ntsb.gov/DS (alg 8, id 14297): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ntsb.gov/DS (alg 8, id 14297): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ntsb.gov/DS (alg 8, id 14297): 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.
- ntsb.gov/DS (alg 8, id 14297): 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.
- ntsb.gov/DS (alg 8, id 62572): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ntsb.gov/DS (alg 8, id 62572): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ntsb.gov/DS (alg 8, id 62572): 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.
- ntsb.gov/DS (alg 8, id 62572): 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.
- 8cbkfuh4iz.ntsb.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- ntsb.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- ntsb.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
