ntsb.gov
Updated:
2021-12-18 00:24:05 UTC (1073 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (10)
- ntsb.gov/A
- ntsb.gov/AAAA
- ntsb.gov/MX
- ntsb.gov/NS
- ntsb.gov/NS
- ntsb.gov/NSEC3PARAM
- ntsb.gov/NSEC3PARAM
- ntsb.gov/SOA
- ntsb.gov/SOA
- ntsb.gov/TXT
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ntsb.gov/DNSKEY (alg 8, id 20340)
- ntsb.gov/DNSKEY (alg 8, id 24355)
- ntsb.gov/DNSKEY (alg 8, id 46288)
- ntsb.gov/DNSKEY (alg 8, id 48033)
- ntsb.gov/DNSKEY (alg 8, id 65305)
- ntsb.gov/DS (alg 8, id 24355)
- ntsb.gov/DS (alg 8, id 24355)
- ntsb.gov/DS (alg 8, id 65305)
- ntsb.gov/DS (alg 8, id 65305)
Delegation status
Secure (2)
- . to gov
- gov to ntsb.gov
Notices
Errors (6)
- ntsb.gov zone: The following NS name(s) did not resolve to address(es): 152.180.40.110
- ntsb.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2600:803:250:1040::110)
- ntsb.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2600:803:250:1040::110, UDP_-_NOEDNS_)
- ntsb.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2600:803:250:1040::110, UDP_-_NOEDNS_)
- hufvknaqb2.ntsb.gov/A 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 (14)
- gov to ntsb.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): 152.180.40.110 See RFC 1034, Sec. 4.2.2.
- gov to ntsb.gov: The glue address(es) for ns.ntsb.gov (199.173.155.4) differed from its authoritative address(es) (152.180.40.110). See RFC 1034, Sec. 4.2.2.
- ntsb.gov/DNSKEY (alg 8, id 20340): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (199.173.155.4, UDP_-_EDNS0_4096_D_KN)
- ntsb.gov/DNSKEY (alg 8, id 46288): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (152.180.40.110, UDP_-_EDNS0_4096_D_KN)
- ntsb.gov/DS (alg 8, id 24355): 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 24355): 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 24355): 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 24355): 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 65305): 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 65305): 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 65305): 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 65305): 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.
- hufvknaqb2.ntsb.gov/A 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.
