inl.gov
Updated:
2022-10-13 13:32:19 UTC (774 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- inl.gov/A
- inl.gov/MX
- inl.gov/NS
- inl.gov/SOA
- inl.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 261)
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- inl.gov/DNSKEY (alg 5, id 1923)
- inl.gov/DNSKEY (alg 5, id 6823)
- inl.gov/DNSKEY (alg 5, id 8669)
- inl.gov/DS (alg 5, id 8669)
- inl.gov/DS (alg 5, id 8669)
Delegation status
Secure (2)
- . to gov
- gov to inl.gov
Notices
Errors (2)
- inl.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (141.221.66.10, 141.221.68.40, 2620:0:2b88:9700::40, 2620:0:2b88:b301::10)
- inl.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (141.221.66.10, 141.221.68.40, 2620:0:2b88:9700::40, 2620:0:2b88:b301::10, TCP_-_EDNS0_4096_D_N)
Warnings (21)
- RRSIG inl.gov/A alg 5, id 1923: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG inl.gov/DNSKEY alg 5, id 1923: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG inl.gov/DNSKEY alg 5, id 1923: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG inl.gov/DNSKEY alg 5, id 1923: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG inl.gov/DNSKEY alg 5, id 8669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG inl.gov/DNSKEY alg 5, id 8669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG inl.gov/DNSKEY alg 5, id 8669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG inl.gov/MX alg 5, id 1923: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG inl.gov/NS alg 5, id 1923: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG inl.gov/SOA alg 5, id 1923: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG inl.gov/TXT alg 5, id 1923: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- gov to inl.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): ns.inl.gov, ns2.inl.gov See RFC 1034, Sec. 4.2.2.
- inl.gov/DS (alg 5, id 8669): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- inl.gov/DS (alg 5, id 8669): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- inl.gov/DS (alg 5, id 8669): 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.
- inl.gov/DS (alg 5, id 8669): 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.
- inl.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- inl.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- inl.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- xdkc4foeta.inl.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- inl.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
